[openstack-dev] [kolla] branching Mitaka March 21, 2016 (important note for CRs)

Steven Dake (stdake) stdake at cisco.com
Mon Mar 21 16:02:32 UTC 2016

Hey folks,

Typically all projects branch at rc1, but originally because we had a mountain of blueprints and bugs after mitaka-3 was released, I sent an email indicating we would branch at rc2.

Unfortunately branching at rc2 is not a viable plan because we are gating the master code base of OpenStack with Mitaka deployment tooling.  Because this could result in us finding master bugs in the mitaka codebase, we are branching now, as soon as we believe the branch is fairly stable which I hope Is today :).

IMPORTANT for Core reviewers,
If any patch until the release of Mitaka has a TrivialFix  flag, please -1 the patch.  All patches need a bug id until Mitaka is released to properly handle backports into the mitaka branch.  If its not in the tracker and targeted for rc2, it won't be backported.  If it is in the tracker and targeted for rc2, it will be backported.  This includes tardy blueprint work.

Since sharing the load on backports hasn't worked in the past, I will take full responsibility for cherry-picking and backporting all bug fixes until Mitaka releases.  Any patch without a bug ID WILL NOT BE BACKPORTED - so please don't approve TrivialFix changes.  Documentation changes are ok without any special tagging.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160321/26104715/attachment.html>

More information about the OpenStack-dev mailing list