On Mon, Jun 13, 2011 at 4:00 PM, Rob Lanphier robla@wikimedia.org wrote:
On Tue, Jun 7, 2011 at 11:57 PM, Ashar Voultoiz hashar+wmf@free.fr wrote:
This is a linear progression, the revision become harder and harder to review since, with time, most of the easy stuff got reviewed :-) Make it a long tail maybe ? :-)
Well, kinda moot at this point. Unfortunately, we're not even beating a linear progression to a July 15 target:
There's been only one data point so far (last tuesday)... so it might be tough to extrapolate yet. :)
I'm not making a big fuss about this until 1.17 is done, since I know,
for example, that Tim has been doing the last bits of detail work necessary for a 1.17 tarball release, so he hasn't been able to make as much of a dent as others have been available for. Still, we're going to need to go faster than this to expect a deploy before August. Thoughts on how to accelerate?
When we were prepping 1.17 for deployment the theory seemed to be that it'd be out the door and *done* within a couple weeks and we'd be able to concentrate on 1.18 from there out and keep up with everything.
That was several months ago... we still haven't released 1.17, there seems to be little or no commitment to a deployment or release schedule on 1.18, and what review has happened between 1.17 and 1.18 has been totally unorganized ad-hoc opt-in poking.
If we're working on the assumption that 1.17 being unreleased is slowing down 1.18 work, then what are we doing sitting around?
Get that 1.17 tarball OUT and move on. It's been "any day now" for like three months...
Give us a deployment date for 1.18 and make it a top priority for engineering.
Give us a release date for 1.18 and make it a top priority for engineering.
-- brion