On Fri, Dec 3, 2010 at 10:42 PM, Roan Kattouw roan.kattouw@gmail.com wrote:
2010/12/3 Rob Lanphier robla@wikimedia.org:
There's some release planning issues that we have to sort out:
- When will we branch 1.17?
Soon, IMO. Branching sooner means stabilizing sooner means releasing and deploying sooner. I don't think there's anything major we want to add to 1.17, right? It's a pretty big release already.
Branching as soon as possible would be nice. I think that there are no very large projects holding this up. But, if we branch too soon, and if we take too long at releasing, we would inevitably run again in a large review backlog on trunk. Therefore when we branch we should be certain that their are no big projects coming up in between that would draw a lot of people from working on the release.
I would prefer branching as soon as possible. Is there a reason too not just branch *right now*? Anybody who wants to be bold?
In addition to that, if we'd have a few paid devs devoting their time to doing review and other things needed to get 1.17 into shape (WMF-employed reviewers are mostly focusing on their assigned projects now AFAICT) I think we can definitely finish before March.
I strongly second getting more paid devs into CR. It worries me a bit that I see certain other projects being developed and deployed, while general code review should be the top priority now.
Bryan