On Thu, Feb 3, 2011 at 3:17 PM, Chad <innocentkiller(a)gmail.com> wrote:
On Thu, Feb 3, 2011 at 5:17 PM, Brion Vibber
<brion(a)pobox.com> wrote:
On Thu, Feb 3, 2011 at 1:07 PM, Chad
<innocentkiller(a)gmail.com> wrote:
On Thu, Feb 3, 2011 at 3:19 PM, Brion Vibber
<brion(a)pobox.com> wrote:
... It might happen for the next quarterly
release, but not this time around.]
Haha, quarterly releases :p
It's never too late to get back on track. :)
Were we ever on track?
1.5.0: 2005-10-05
1.6.0: 2006-04-05 (first scheduled quarterly release)
1.7.0: 2006-07-06 - 3 months
1.8.0: 2006-10-10 - 3 months
1.9.0: 2007-01-10 - 3 months
1.10.0: 2007-05-09 - 4 months (a little late)
1.11.0: 2007-09-10 - 4 months (a little late)
1.12.0: 2008-03-20 - ~6 months (missed one quarter)
1.13.0: 2008-08-14 - ~5 months (missed one quarter)
1.14.0: 2009-02-22 - ~6 months (missed one quarter)
1.15.0: 2009-06-10 - 3.5 months
1.16.0: 2010-07-28 - 13.5 months (missed 3 quarters)
So roughly: 2006 & 2007 were pretty well on track, with some slight slides
due to extra beta & release candidate testing on 1.10 and 1.11. Things then
started to slide a bit with 2008 & early 2009's updates slipping to
semiannual, but we got back on quarterly track with summer 2009's 1.15
release.
We then have a big empty spot where it took over a year to get 1.16 pushed
through to stable release. I get the impression that a large part of this
delay was that there was no clear consensus on the js2 stuff; once that got
re-imagined as 1.17's ResourceLoader which got more buy-in, 1.16 was able to
get a cleaner release without the next-gen JS code, and 1.17 has been able
to concentrate more on that layer of things.
1.17 releasing soon should bring the schedule back to semi-annual, but
there's no firm impediment other than our own self-organization to pushing
1.18 out 3 months later instead of 6 or 13.
-- brion