[TYPO3-core] RFC #12022: PHP-5.3 warning about missing references with some extensions

[Oliver Hader]

Hi Franz,

Franz Holzinger schrieb:
> Dan Osipov a écrit :
>> If 1.2.1 is incompatible with 1.2.0 it should have been named 1.3.0 or
>> 2.0.0 to begin with. Last decimal is for small bugfix releases, such
>> as what is described in this case.
>>
>> Dan Osipov
> Yes, but in most cases you will realize the incompatibility in some
> cases after and not before you upload into TER. And you cannot fix this
> any more.
> And IMHO many users want to see major feature changes when the second
> version number changes.

Yes, that's also the reason why Mircosoft publishes new versions like
Windows Vista or Windows 7... They do not put everything into Windows
3.11 and release it again in 2009.

I don't see the point. If an extension needs an update - for whatever
reasons - the version number is increased. Reusing version numbers while
the code changed does not make sense. Imagine discussions like "Do you
use version 1.2.0 from February 2007 or version 1.2.0 from August 2009?"

To get back to the topic: It's not TYPO3 that changed the behaviour.
It's PHP 5.3 that did. I guess there have been reasons for that - we
cannot reimplement PHP 5.2 in TYPO3...

olly
-- 
Oliver Hader
TYPO3 Release Manager 4.3