[Typo3-dev] TYPO3 version 4.0.0?

[Daniel Hinderink [TYPO3]]

> Daniel Hinderink [TYPO3] wrote:
>> Hi Kasper,
>> 
>> 
>>> I feel we are somehow locked into a bad version number cycle.
>>> 
>>> The next version of TYPO3 has been announced as 3.6.0. This is a step of
>>> 0.1 over 15 months!
>>> And if you look at the future plans for the core it is all about changes
>>> that cannot fairly be said to justify a jump to 4.0.0 more than the
>>> current release.
>>> 
>>> In one way we could say we don't care. But psychologically it might not
>>> be wise to stay with "3.6.0, 3.6.1, 3.7.0,.... 3.11.0" etc. I think it
>>> would be more close to the truth if we moved like "4.0.0, 4.0.1, 4.5.0,
>>> 4.6.0, 5.0.0" etc.
>>> 
>>> Please understand that I'm not suggestion to inflate the version numbers
>>> beyond recognition. I just think we are too "humble" currently (and
>>> traditionally!)
>> 
>> It is quite funny to have that coming from the development side of things.
>> Normally the evolution of version numbers is merely a technical matter and
>> marketing is trying to inflate these.
> 
> My view on a 4.0 that deserves this name is quite radical:

I would call that progressive, not radical :-)
 
> A major version number has the advantage that it signifies major
> changes. This is a chance for weeding out cruft. I'm thinking of stuff
> like language strings in the split syntax. Old functionalties that have
> been replaced by much better constructs and have been deprecated for a
> long time.

I would rather like to put that on the list for a seperate v5 development
path and let the next "normal" release be a 4.0. 4.0 is fine if we can make
a strong case based on real-world advantages it is offering. E.g. DBAL with
actual fully functional support for at least Oracle and MSQL.

This will finally be the measure by which to decide wether anything makes
big news or not. It seems many people believe marketing means giving things
pretty names and glitzy appearences. But in fact these help nothing much, if
there is no beef. So let's concentrate on the beef, not the glitz.

> I'm not meaning to burn down all bridges, but risking slight
> incompatibilites for installatoins and extensions that have gathered
> dust. Something like 99,9% compatibility if the code is reasonable
> up-to-date.

In fact there is no need to be afraid about backwards incompatibilities if
the trade-off is right and the new versions offer persuasive advantages. And
it will mean money for all of us who will migrate our customers. People are
used to paying for major updates and there is nothing wrong with that.
It should just not happen every release.
 
> Masi who not only loves to rename stuff but likes a clean code base

value first!

Daniel


> 
> _______________________________________________
> Typo3-dev mailing list
> Typo3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
> 

-- 

Daniel Hinderink
TYPO3 - get.content.right
Innovation, Marketing, PR
http://www.typo3.com

-- 
If the world should blow itself up, the last audible voice would be that of
an expert saying it can't be done.
Peter Ustinov