Given that Hryum has been asking us all to help him out with making
releases, I suppose we could try to take advantage of the load being
spread among more than, er... one person, and issue patch releases
in a slighly more frequent basis.
Here are the release dates of 1.7.x releases issued so far:
1.7.0 - 11 Oct 2011
1.7.1 - 24 Oct 2011
1.7.2 - 02 Dec 2011
1.7.3 - 14 Feb 2012
So the gap between releases has been widening, from roughly 2 weeks
for the first batch of fixes, to currently 2.5 months.
1.7.3 was released one week ago. If the current trend continues,
1.7.4 would be released sometime in April.
However, I can already count 11 nominations in STATUS on 1.7.x,
some of which miss only a single vote, and some of which fix some
rather annoying regressions (yes, externals, I'm looking at you).
I think we should be able to ship those fixes during the first or
second week of March. This would mean starting the release train
at the end of next week, and trying to get a decent amount of voting
to happen throughout next week.
I would try to run this release if Hyrum doesn't have time to do
the 1.7.4 show. I haven't re-read the release-process documentation
yet and I certainly hope that Hyrum will be able to assist me if needed :)
But if any errors creep into the process, we can still delay the
release for a week or so without running much risk of anybody out
there becoming too impatient.
Would people be happy with this?
Received on 2012-02-22 19:05:31 CET