Cake 2.0 Roadmap - must it be all at once?

Please don't throw eggs, but..

...after looking over the 2.0 roadmap, I am wondering about the
relative benefit of major "shock and awe" releases vs. the
continuation of the successful 1.x pattern of smaller, but still
significant, incremental releases (where applicable).

I am a tad concerned the 2.0 roadmap might be taking on too much for
one release.

In particular, I am wondering if there is any remote possibility for
the development team to consider the division of 2.0 into a series of
smaller releases, rather than a whopping "grand 2.0" one shot
delivery?

For example (just an example), might it be feasable to release a 2.0
with the only new PHPUnit testing framework, on a php5-only base?

People can use it to start writing their new tests, migrating their
old ones, in parallel with 2.1 development.

Over the next few releases, there can be a phase in of the rest of
lazy loading, removal of PHP5 hacks, E_STRICT compliance, interfaces/
abstract classes/exceptions , etc.

This will enable quicker deployment of new features to the community,
and as a result engender quicker feedback to the developers through
more parallel usage of the releases. It somewhat derisks things, and
keeps the ball moving.

Comments?

Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.

You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en