[TYPO3-core] Memory system woes
Thorsten Kahler
thorsten.kahler at typo3.org
Wed Feb 13 10:53:41 CET 2013
Michael Stucki schrieb am 13.02.13 00:45:
>
> The learning should be:
> - Code cleanup will improve the maintainability of the overall code
> and should be encouraged
> - Performance should not be removed without having a follow-up patch
> at hand that improves the situation again
>
> Anything else to add?
>
Of course!
- Communicate before commit. Major refactorings, especially if they have
to be split into many patches (as usually) or if they affect
performance, resource usage, environmental dependencies etc., should be
discussed or at least published beforehand. It's nice that Lolli opened
up some details and thoughts about ext_tables.php refactoring, but he
wouldn't have done without Tolleiv raising his hand.
After having more than enough communication disasters last year we
should at least try to improve in this area.
Just my 2c
Thorsten
--
Thorsten Kahler
TYPO3 CMS Core Team member
TYPO3 ... inspiring people to share!
Get involved: typo3.org
More information about the TYPO3-team-core
mailing list