On 02/13/2013 12:45 AM, Dan Wendlandt wrote: > Ok, folks, > > We're now one week from the branching G-3, and this means G-3 is > officially close to any blueprints that are not already in code review. > > <soapbox> Now we now need to shift our focus to making sure that Grizzly > is a stable & well-documented release. To insure stability, we need to > make sure that even items already in review are only merged if they are > of high quality and been through a thorough review. A feature merged > just so it can make it before a deadline will result in additional bugs > that need to be fixed, reviewed, and discussed during a time when we > really need to be focused on testing + documenting to make users of > Quantum Grizzly successful. </soapbox>
I made the decision yesterday evening to not try to get the ml2 plugin into grizzly. It needs at least a few more days of work before its ready for serious review, and I think it would really benefit from a more meaningful review after crunch time than it could possibly get this week. I expect to submit WIP updates as I make progress, and hopefully have this ready for official review soon after grizzly crunch time ends. I would appreciate if all quantum core developers could at least make a point of taking a look at it prior to the summit so we can make some decisions about its role going forward. For now, I'll be putting most of my time available for upstream work into grizzly bug fixes, reviews, and documentation. -Bob > > At this point, no work should be merged without a blueprint or bug that > is targeted at G-3. If you're a sub-team lead, please identify any G-3 > blueprints under review that aren't getting enough attention, and ask > the developer to either get two active cores to sign up for the review, > or two move it out of Grizzly. Also please keep an eye on G-3 bugs in > your area filed to make sure they are small and focused changes. Mark > will be leading bug triage, and highlighting high priority issues that > are not currently assign. > > Finally, documentation is something we got started on WAY to late in > Folsom, and I don't want to repeat that mistake in Grizzly. Since the > feature-set of Grizzly is now fixed due to the freeze, as a sub-team > lead, please review issues from G-1 through G-3 and make sure there are > documentation bugs filed for each of them (both Admin + API docs, as > necessary). If possible, please update the whiteboard of the issue with > a link to the doc issue(s). For items still in review, please do not > merge a feature until all appropriate doc bugs have been created. Two > weeks from now, our team meetings should be focused almost entirely on > doc + bug fixes. > > There's a lot of reviewing, bug fixing, and document to be done. Please > reach out to the team list or me early on if an issue arises, so we > don't leave things until the final review days. This week tends to be > the most demanding week of the entire release cycle, so I want to thank > everyone in advance for your effort during the big review crunch. See > you all on gerrit! > > Dan > > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Dan Wendlandt > Nicira, Inc: www.nicira.com <http://www.nicira.com> > twitter: danwendlandt > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > -- Mailing list: https://launchpad.net/~quantum-core Post to : [email protected] Unsubscribe : https://launchpad.net/~quantum-core More help : https://help.launchpad.net/ListHelp
