[development] Freezing the Drupal API

[Morbus Iff]

>> My aim would be that as of Drupal 5.0 with CCK, the published
>> API would be treated as "stable" and changes to it would be
>> resisted strongly.

I tend to agree with killes: Drupal's policy, since as long as I've 
known it, is to give nary a look to backwards compatibility, and that is 
incredibly *freeing* when it comes to *strong* development. This isn't 
to say that we don't understand that there is an issue with the 
inevitable upgrade, but this is why we:

  * provide instructions on theme and module upgrades.
  * don't release an update until the major third party
    components of Drupal are already upgraded.

Roughly though, this sort of discussion comes up once every six months.

-- 
Morbus Iff ( don't heckle the super-villain )
Technical: http://www.oreillynet.com/pub/au/779
Culture: http://www.disobey.com/ and http://www.gamegrene.com/
icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus