[development] Freezing the Drupal API

sime info at urbits.com
Tue May 16 01:34:34 UTC 2006

Hi Richard
Sorry, I don't understand.

Why would you want to upgrade if you haven't built the cost into your 
product? All you *need* to do is patch security holes.

What is wrong with continuing to run drupal 4.5? The last place I worked 
still uses MS Office 97 which is almost 10 years old.

I think you should charge large companies more and hence have the funds 
you need to follow the upgrade path (if that is necessary).


Richard Archer wrote:

>Hi all,
>Recent discussions on the Consultants list has raised the issue of
>the cost of doing business using Drupal, notably the high cost of
>upgrading existing installations due to the ever-changing nature
>of Drupal's API.
>I wonder if there would be any interest in forming a group to
>tackle this by identifying where the current API has potential
>for improvement and perhaps even writing some code!
>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.
>IMHO, if this could be achieved it would give Drupal a much more
>mature look and make it more attractive to large users.
>It would also increase the manpower available to work on future
>Drupal development because right now extra resources are being
>wasted maintaining the 4.5 and 4.6 trees, simply because the API
>changes between releases makes it impractical for many users to
>upgrade to 4.7.
> ...Richard.

More information about the development mailing list