[TYPO3-mvc] Missing documentation/examples for Extbase 1.4 features

Jigal van Hemert jigal at xs4all.nl
Tue Dec 6 23:45:08 CET 2011


Hi,

On 6-12-2011 22:15, Ernesto Baschny [cron IT] wrote:
> For sysext in general there has been the idea around the core team to do
> that. But plenty of those sysext's have no activity or enhancements
> during certain releases (or since ages), so it makes no sense to just
> "increase" its version number while nothing changed. Having the versions
> independent from the TYPO3 version allow the integrators to see where
> there have been changes at all (and where "major" and where only "minor").

This implies that someone actually checks for all sysexts if there are 
changes in a version and increases the version if that is the case?

> So to "sync sysext version with TYPO3 version" only makes sense to the
> few sysexts which are really actively being enhanced by some team (e.g.
> Extbase, Linkvalidator, Workspaces, ...) during more than one release.

It makes sense for all sysexts. They were tested with that particular 
release and so the em_conf should reflect that they are suitable for one 
or more versions. Keeping the sysext version in sync with the TYPO3 
version makes it all a lot simpler. When preparing a new version (a 
"major" version) (after the release party of the previous version) all 
sysexts can be set to be compatible with 4.x.0-4.x.99 and the version 
can be synced with that new version.

Bugfixes, feature can go to the appropriate branches and will only be 
used with the TYPO3 version they are meant for.

-- 
Kind regards / met vriendelijke groet,

Jigal van Hemert.


More information about the TYPO3-project-typo3v4mvc mailing list