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

[Dan Osipov]

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
Calkins Media
http://danosipov.com/blog/

Franz Holzinger wrote:
> Ingmar Schlecht a écrit :
>> Franz Holzinger schrieb:
>>> Ernesto Baschny [cron IT] a écrit :
>>>> Franz Holzinger schrieb:
>>>>> Martin Kutschker a écrit :
>>>>>
>>>>>> I don't think that $content and $conf were ever meant to be passed by
>>>>>> reference. So IMHO it's the
>>>>>> extensions that should be changed, not the Core.
>>>>> You cannot change all the extensions which are already in TER. Or can
>>>>> you?
>>>> But the extension author can. His extension does not work with PHP 5.3
>>>> and he should / can fix it if he wants it to work with PHP 5.3. It is
>>>> not TYPO3's fault.
>>> So does this mean that it allowed to reupload an extension under the
>>> same version number?
>>> AFAIK it is not possible to change the file ext_emconf.php for an
>>> already uploaded extension. So all users who upgrade to PHP 5.3. would
>>> have no working sites any more.
>>
>> Hmm? Why not just increas the version number?
> 
> A user has extension my_key in version 1.2.0 on his site. A version 
> 1.2.1 already exists in TER. So how do you want to increase the version 
> number? Maybe version 1.2.1 is not compatible and he does not want to be 
> forced to upgrade.
> So this would mean that the users are forced to wait until they are able 
> to update multiple extensions, if you are not allowed to upload it again 
> under the same version number into TER.
> 
> - Franz