Victor Kane wrote:
On 1/31/07, James Walker <walkah@walkah.net> wrote:
On 1/31/07 5:30 PM, Victor Kane wrote:
I sort of perhaps naively assume that it would make no sense making another major release without dealing with those problems.
It's an interesting point. One thing to keep in mind, however, is the mental effect of having a "hard" deadline. As anyone who has been around for a few release cycles can attest - there is a disproportionate flurry of patch submissions "at the deadline". So having a "hard" deadline is largely motivational. To get people thinking & started on their "big ideas" for the next drupal.
Drupal always has, and always will be 'released when ready'.
That's great, I'm all for that. I am simply concerned because I don't see any correlation between announced new functionality
Where was any new functionality announced?
and the estimation of four months, and even less, an iterations plan. I
It's open source. That doesn't exclude a plan, but in Drupal's case there really isn't one.
suppose that drupal veterans may have a clear picture, but I advise that the target functionality be gleaned from the feature request list and prioritized.
We've never cared about feature requests too. Individuals may have, but not the project as such. Cheers, Gerhard