Martin Tomes wrote:
Boerland, Bert wrote:
-----Original Message----- From: development-bounces@drupal.org
A time based release cycle has merits.
The Subversion project has been through this argument, it might be profitable to read their policy:
http://subversion.tigris.org/roadmap.html
They also have a very clear compatibility statement which Drupal could benefit from: API compatibility through all minor releases:
http://subversion.tigris.org/hacking.html#release-numbering
This doesn't stop new interfaces being added and old ones deprecated but it does mean the deprecated interfaces will exist until the next major release.
There is no way I will ever be in favour of backwards compatibility in Drupal. We keep our apis stable throughout our minor release numbers and that's it. Everybody can update some php files once or twice a yeah. And if they don't feel its worth it: Nobody has to upgrade either. Cheers, Gerhard