release candidate++ 6 month pre-defined release schedule ++ Some thought will have to be given for how long a window should be open for new features. I'm thinking 3 months with the alpha released at that point. 4 months is the target for beta, 5 months target for release candidate. In the best scenario, we coast through the last week of the release candidate period wondering if any more bugs will be discovered. Drupal 5.0 would have seemed appropriate, but it's too late. -Robert Dries Buytaert wrote:
(Crazy idea: should 4.7 be renamed 5.0? Would it be better to call it 5.0?
It would have been, but with several beta's already released it's now too late. And besides if everyone listens to Adrian R. and implements his crazy/brilliant ideas 4.7 *will* look like a point release compared to 4.8... =D
There a lot of crazy (yet cool) ideas shaping up for Drupal 4.8/5.0. People should already start preparing their patches; I hope to use much shorter development cycles in future aiming towards 2-3 releases a year. I'm thinking about trying a time-based release cycle, where development is frozen at a predefined date. It sounds like something worth evaluating. It doesn't hurt to give it a try.
-- Dries Buytaert :: http://www.buytaert.net/