I would personally like to request a code freeze at least one week earlier than that; the second week of August would be nice. My reasons are mostly but not completely selfish. -Robert Dries Buytaert wrote:
I won't switch to strict time-based releases, nor to strict feature- based releases, though I'm willing to lean more towards time-based releases. I very much prefer to release when (i) we made enough improvements and (ii) it has been a while since we released a new version. Contrary to what some people say, the Drupal release schedule has been fairly predictable for those who are part of the Drupal community.
That said, I was planning to announce a new code freeze shortly -- I meant to do it last week but was swamped with work. Either way, I was thinking about starting the next code freeze on September 1 (5 weeks from now). This means Drupal 4.7 will be released somewhere in October or November.
On 24 Jul 2005, at 11:06, Karoly Negyesi wrote:
Let's start making a calendar for next year's releases now and stick to it.
My proposal:
2005 dec 26 code freeze (or Jan 2, 2006) 2006 feb 6 Drupal 4.8 2006 may 1 code freeze 2006 june 5 Drupal 4.9 2006 aug 28 code freeze 2006 oct 2 Drupal 5.0 2007 jan 1 code freeze 2007 feb 5 Drupal 5.1 ...
-- Dries Buytaert :: http://www.buytaert.net/