Open Stack

The purpose of the stable branch and the maint team that theirry mentioned earlier is to vet patches.  Are you suggesting that we need a point release system for openstack outside of relying on distros to pick release points?

Vish

On Dec 6, 2011, at 1:21 PM, Tim Bell wrote:

> 
> We need more than 'just' packaging.... it is using the testing, documentation and above all care to produce *and* maintain a stable release that production sites can rely on for 6-12 months and know that others are relying on it too.
> 
> Who is going to make the judgement that a bug fix to the latest Essex development branch is a valid patch for a backport to stable/diablo and does not break production sites ?
> 
> Diablo 2011.3 brought much functionality but also some useful points to consider for the future as to how we organise the project.
> 
> Tim
> 
>> 
>> (4) OpenStack will accept and foster a new project, one that is not 
>> focused on development, but rather the distribution and it's general 
>> stability. This distro project will be responsible for advocating on 
>> behalf of various operating systems/distros/sponsoring vendors for 
>> bugs that affect performance and stability of OpenStack, or prevent an 
>> operating system from running OpenStack.
>> 
>> Thoughts?
>> 
>> d
> 
> Hi
> 
> We already have an little informal channel on freenode called #openstack-packaging.
> 
> Regards
> chuck
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp