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.
From: Aleksandra Fedorova
Sent: Wednesday, September 10, 2014 2:45 PM
To: firstname.lastname@example.org, fuel-core-t...@mirantis.com
as a follow-up for discussion  we created stable/5.1 branch for all Fuel
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.
OpenStack-dev mailing list