[development] One core, many distributions

Darrel O'Pry dopry at thing.net
Wed Nov 23 16:37:34 UTC 2005

On Wed, 2005-11-23 at 17:15 +0100, Dries Buytaert wrote:
> > These modules will have to be rewritten for 4.7 to do exactly the  
> > same thing they are already doing. This will take time. Time = money.
> if (benefits > costs) {
>    upgrade_to_47();
> }
> else {
>    stick_with_46();
> }

> Clearly, there is a tension between breaking backward compatibility  
> and not breaking backward compatibility.  Unfortunately, there is no  
> "winner" because the costs can't be quantified.  Not the absolute  
> costs.  Not the relative costs.  I'm in the camp that, we are best of  
> breaking backward compatibility when necessary; it buys us  
> maintainability and flexibility, which, in turn, makes for a longer  
> product lifecycle.

And more billable development hours if you play your cards right ;).
I'm in the same camp. I was poking through some of the earlier versions
of drupal... I think the changelogs indicated late 90's early 00's...
I'm glad drupal isn't 100% backwards compatible.

More information about the development mailing list