Yes, that's correct. Of course, there is significant overhead in cherry-picking changes, so it's in your interest to complete as many bug fixes as possible before you branch.
David On Mon, Feb 27, 2017 at 7:40 AM, Georg Kunz <[email protected]> wrote: > Hi David, > > > > I suppose you mean closing the window for cutting the stable branch. The > branch itself will remain open for bug fixes, right? > > > > Best regards > > Georg > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *David McBride > *Sent:* Saturday, February 25, 2017 5:26 AM > *To:* [email protected]; TECH-DISCUSS OPNFV < > [email protected]>; Tapio Tallgren < > [email protected]>; Raymond Paik <[email protected]> > *Subject:* [opnfv-project-leads] [release] Danube stable branch date and > time > > > > Team, > > > > I took an action at the last release meeting to specify a specific time > for closing the stable branch on March 10. We will close the stable branch > at 12 p.m. (noon PST) on March 10. > > > > Note that I have another action that is in process to update the stable > branch instructions for Danube. I will email the team when those > instructions are available. > > > > Let me know if you have any questions. Thanks. > > > > David > > > > -- > > *David McBride* > > Release Manager, OPNFV > > Mobile: +1.805.276.8018 > > Email/Google Talk: [email protected] > > Skype: davidjmcbride1 > > IRC: dmcbride > -- *David McBride* Release Manager, OPNFV Mobile: +1.805.276.8018 Email/Google Talk: [email protected] Skype: davidjmcbride1 IRC: dmcbride
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
