[TYPO3-core] RFC #10497: Mark t3lib_div::makeInstanceClassName() as deprecated

Niels Pardon mail at niels-pardon.de
Mon Mar 2 15:26:53 CET 2009


Hi Ingo!

Ingo Renner schrieb:
>> The only way to avoid this for an extension author is to have two
>> branches of his extensions. One which uses the way in<  4.3 and one
>> which uses the way in>= 4.3.
> 
> This is not the only way, but another quick possibility is the one
> outlined by Dmitry. However a branch would be a very clean way.

I don't understand why TYPO3 officially maintains two release lines but
an extension should not be able to support two release lines?

If we would have a "soft depreciation" without a warning in 4.3 then
extensions could still support 4.2 and 4.3. As soon as 4.4 comes out
support for 4.2 can be dropped by extension authors, too.

Greets,

Niels


More information about the TYPO3-team-core mailing list