Open Stack

Please also note, that all open patches created *before* the stable/5.1 branch should now be reconsidered as targeted to 6.0 release instead of 5.1 as they initially were upon the submission. 

Therefore, all backporting stuff needed should be not forgotten and related bugs should be updated as appropriate. 


E.g. bug  https://bugs.launchpad.net/fuel/+bug/1366712 initially was nominated for 5.1 milestone only, but after the stable/5.1 branch creation, it was updated in order to reflect all its new backporting status as well. 


Also note, if there were no more patches but one 5.1 targeted (i.e. master branch, before stable/5.1 creation), related bugs should be updated as 6.0 in progress and 5.1 as not started(confirmed) or triaged - in order to not forgot to backport it later once merged in master branch.


Please let’s not forget an important backports.


Best regards,

Bogdan Dobrelya.





From: Aleksandra Fedorova
Sent: ‎Wednesday‎, ‎September‎ ‎10‎, ‎2014 ‎2‎:‎45‎ ‎PM
To: openstack-dev at lists.openstack.org, fuel-core-team at mirantis.com









Hi, everyone,


as a follow-up for discussion [1] we created stable/5.1 branch for all Fuel projects.

Since now on all patches targeted for upcoming 5.1 release should go to master branch first and then should be cherry-picked to stable/5.1.


CI Infrastructure branching is in progress. With any branching-related issues please contact devops team at #fuel-devops IRC channel.






[1] https://www.mail-archive.com/openstack-dev%40lists.openstack.org/msg34607.html



-- 



Aleksandra Fedorova
bookwar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140911/058bb99b/attachment-0001.html>