[TYPO3-core] Backporting Hooks

[Jigal van Hemert]

Hi,

On 18-2-2013 15:56, Kay Strobach wrote:
> after the discussion, what is the result?

Flu made me miss the discussion :-)

>> As Tolleiv mentioned in the "Review System woes" sometimes Hooks are
>> missing in the core. So my question is, if hooks may be backported in
>> the future.
>>
>> Reasons:
>>   - Having hooks backported reduces the use of XClasses
>>     (which should be denied in my opinion)

True. (You want XCLASSes entirely removed??)

>>   - Having Hooks instead of XClasses reduces headaches between version
>>     switches

Well, it adds some headaches if you introduce them in bugfix releases. 
How would you handle compatibility with 4.5.21 or higher in the 4.5 
branch, 4.6.7 or higher for the 4.6 branch, etc. It's impossible to set 
that in the dependency settings.

>>   - Hooks usually do not break anything, but offer more possibilities :D
>>   - Having Hooks backported atleast one version / LTS makes it easier to
>>     make futureproof extensions

I think you mean that not using an XCLASS would make it more likely that 
it would work with a next version?

There are advantages to backporting them, but the main problem (besides 
the rule of no features in backports) is that compatibility with certain 
versions is hard to communicate.

-- 
Jigal van Hemert
TYPO3 Core Team member

TYPO3 .... inspiring people to share!
Get involved: typo3.org