[TYPO3-dev] Are performance improvements part of maintaince releases?

Steffen Kamper info at sk-typo3.de
Fri Jun 26 09:22:52 CEST 2009


Hi Michael.

Michael Stucki schrieb:
> Hi Steffen,
> 
>>> Did you ever had a look how the rest of the universe handles this?
>>
>> thanks for that examples. For me it shows that performance boost is 
>> worth for updates without having change of behaviour.
>> I don't know why so many fear that they loose a "stable" version. Look 
>> at the bugfixes - the release wasn't stable, as the fixes shows. And 
>> who ever fears shouldn't update.
> 
> I'm surprised to read this. Are you serious about it?
> 
it's kind of definition of "stable". For me even trunk is stable, i use 
it in production as well. I don't think that anything will be committed 
that break functionality really, but some bugs are normal in different 
situations.

>> And - performance boost is a good selling argument for the clients. 
>> The normal case is that you sell the client the update. Best reason: 
>> security enhancements. Security is important for each client. Then, 
>> performance is very important too, it gives a feeling of a 
>> professional product. But this is only marketingwise.
> 
> I don't know anyone who sells updates between patchlevel versions. I 
> consider this is part of the product guarantee you have to cope with - 
> so do we.
> 
this also depends on the deal with the client.

>> And - all is a continuing process - new bugs will be found, fixed and 
>> committed for the next release, where i come back to the wanted 
>> situation of having more releases at all in the same time.
> 
> Me too! :-)
> 
so let's do :-)

vg Steffen




More information about the TYPO3-dev mailing list