Speaking of 20% code review time, I've cleared my Tuesdays and stuck reminders in my calendar so I don't lose track of it in coming weeks. ;)
Please poke me during PST office hours with patches, bugs, and commits that need review or cleanup! -- brion On Nov 21, 2011 6:41 PM, "Rob Lanphier" <[email protected]> wrote: > On Mon, Nov 21, 2011 at 3:52 PM, Brion Vibber <[email protected]> wrote: > > 1.18 hasn't been released yet, so presumably we're still concentrating on > > solidifying the 1.18 release in CR. Per previous discussions about the > 1.17 > > release delays I would have expected this to have gone *really fast* and > > been out the door around mid-October, within a few days of going live on > > the main sites. > > /me reminds Brion IRL just how nutty mid-October was for WMF tech staff. > :) > > It's also Sam's first release, so it's taking a bit longer than if Tim > were 100% focused on it. But the good news is that we're nearly > there. > > > It appears we have gotten to a "release candidate" as of last Friday, > which > > is a good sign; is a final .0 release slated yet? > > We would probably push it out this week, but there's a security bug > we're taking a look at. > > > In the meantime we've got no upcoming 1.19 deployment pressure and nobody > > assigned to ongoing code review, so there's nothing to compel further > > action -- it's not surprising to me at all that it's falling behind. > > Brion and I spoke in real life right after this, which is highly > unfair to the rest of you, but it was really efficient for us. Here's > the gist: > * I've already started a campaign to remind people of the 20% policy > (http://www.mediawiki.org/wiki/20_percent ) > * I'll also be sending out a revised target date for 1.19, based on > looking at the updated numbers and how quickly we reviewed in some of > our more determined review sprints, figuring in some time for a little > regression during the holidays. > * More people from Platform Engineering will be reinforcing that we > want the next release to happen soon, even if that means other things > (e.g. Git migration) lag as a result. > > Not a perfect answer, but I think we're improving with each release. > This time around, one key difference will be clearing the review > backlog before branching, which, with any luck, means less backporting > hell. > > Rob > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
