[TYPO3-core] [TYPO3-v4] TYPO3 4.6 --rebase: pending new features

Xavier Perseguers xavier at typo3.org
Thu Jul 14 14:13:07 CEST 2011

Dear community,

A tremendous work has been done between alpha2 and alpha3. Many thanks!!!

As of today, 19 days to the feature freeze, we have 77 open features:


Some of them are already under review on Gerrit, some of them don't have 
a patch.

I seriously doubt we will be able to tackle all of them but it's not an 

Here's my personal wish list of what should be kept and dealt with, _at 
least_ (reverse-ordered by id):

- [28171]: User friendly page link information in TCEforms
- [27956]: Speed-up backend and allow compression in frontend
- [27694]: Integrate hook dispatcher
- [27493]: Show localization mode of field in form
- [27160]: Do not delete uniqueArray in TYPO3 4.6.*
- [25836]: Monitor peak memory usage
- [25338]: Provide maintenance scheduler tasks (DB optimization, ...)
- [25333]: Remove support for old versions of IM/GM
- [25084]: Content rendering: Table cell content always wrapped in <p>
- [24849]: Upgrade wizard usability
- [21257]: Integrate Security section to Install Tool
- [20877]: Optimize database queries to session tables
- [20500]: Change the DB backend to use a default cache table
- [19791]: Use native SoapClient implementation of PHP5 only
- [19283]: page cache is not influenced by tt_content.starttime/endtime
- [18100]: Use exceptions to detect missing user function
- [17881]: Enable stdWrap for select.where


- [25337]: Add PHP 5.3 namespace support (was proposed as well as part 
of "init.php refactoring" workshop during T3DD11)

As said, some of them are already under review and other needs feedback, 
possibly to close them right away!

The way to beta1

What is very important to me is that even if feature freeze is on 
August, 2nd (as said 19 days left), I'm not willing to integrate huge 
changes such as PHP 5.3 namespace support the day before before as we 
would be sure to have a broken release then.

Beta1 is not meant to be bullet-proof of course but integrated features 
should be stable enough to:

1) work in most cases
2) being sure they can reach the true stability until RC1 (October, 11th)

Just to make sure we all speak the same language, RC1 is ideally the 
version we will ship on October, 25th and no other release candidate 
will have to be released in the mean-time. In short, the date I'll 
advertise in bold right after the feature freeze is the release 
candidate date :-)

Keep up this good work! Thanks!



[17881] http://forge.typo3.org/issues/17881
[18100] http://forge.typo3.org/issues/18100
[19283] http://forge.typo3.org/issues/19283
[19791] http://forge.typo3.org/issues/19791
[20500] http://forge.typo3.org/issues/20500
[20877] http://forge.typo3.org/issues/20877
[21257] http://forge.typo3.org/issues/21257
[24849] http://forge.typo3.org/issues/24849
[25084] http://forge.typo3.org/issues/25084
[25333] http://forge.typo3.org/issues/25333
[25337] http://forge.typo3.org/issues/25337
[25338] http://forge.typo3.org/issues/25338
[25836] http://forge.typo3.org/issues/25836
[27160] http://forge.typo3.org/issues/27160
[27493] http://forge.typo3.org/issues/27493
[27694] http://forge.typo3.org/issues/27694
[27956] http://forge.typo3.org/issues/27956
[28171] http://forge.typo3.org/issues/28171

Xavier Perseguers
Release Manager TYPO3 4.6

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

More information about the TYPO3-team-core mailing list