[drupal-devel] Tight release cycles
killesreiter at physik.uni-freiburg.de
Sun Jul 24 21:35:35 UTC 2005
On Sun, 24 Jul 2005, 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
> We always have five weeks for bug fixing and three months of features.
I obviously like the idea. More releases would mean that new features
would be faster available to users and the requests for backports would go
down. Since the changes between releases wouldn't be that big anymore the
needed work per upgrade would also be less.
More information about the drupal-devel