[TYPO3-dev] New version scheme for system extensions

[Ernesto Baschny [cron IT]]

Hi,

in my (personal) opinion I prefer to stick to version numbers which 
makes sense for each individual extension. I see no reason to just "keep 
rising" version number of extensions on every patch level release even 
if nothing changed. Even between minor updates (4.5 -> 4.6), if there 
has been no changes in a particular sysext, why upgrade their version?

I have seen site integrators comparing sysext version numbers after an 
TYPO3 upgrade just to see if something "changed" (i.e. felogin 
extension). So they have also a good use as "stand alone" numbers.

Extbase stands a bit in a different light because it provides an API and 
features which other extensions heavily rely on, and there is relevant 
documentation, tutorials etc refering to it. And there is an active team 
working on it and there are in fact new features on every TYPO3 release 
(which does not happen to most other sysext). It might be confusing (and 
redundant) to always point to the Extbase PLUS the TYPO3 release name 
(as I have suggested, which at the current phase seems the best compromise).

So +1 to do it for Extbase (and Fluid as a consequence) but -1 for doing 
it on *every* sysext (or even to "automate" this version increasing on 
release time), because it gives site integrators false impression of 
"major changes".

But then you have to stick on updating the version number on every patch 
level release (even if nothing changed), because it would be even more 
confusing of having e.g. Extbase 4.6.1 shipped in TYPO3 4.6.9.

Cheers,
Ernesto

Am 16.12.2011 10:06, schrieb Patrick Lobacher:
> Hi everybody,
>
> started with a little confusion about the version names for Extbase (1.4
> is included in TYPO3 4.6, 1.3 in TYPO3 4.5 LTS, ...) we have discussed
> [1] that it could be very transparent for everybody to have system
> extension version names which reflect the corresponding TYPO3 version.
> Each of the system extensions are tested with a specific TYPO3 version
> so they belong together.
>
> In the recent version of TYPO3 4.6.0 I discovered a lot of different
> versions there, e.g.: 1.0.0 (Import/Export), 1.1.0 (File > List), 1.2.0
> (System Reports), and so on ... but a few extensions versioned with
> 4.6.0 (Extension Manager, Workspaces Management, Versioning Management,
> TYPO3 Skin). This is really confusing for everyone - including me ;-)
>
> So my suggestion is as follows:
>
> - Renaming of the version of *all* system extensions to the TYPO3
> version - beginning at 4.7.0
> - Increasing of the version every time a new version of TYPO3 will be
> released even if there is no change to the extension itself
>
>
> What do you think?
> Patrick
>
>
>
> [1]
> http://lists.typo3.org/pipermail/typo3-project-typo3v4mvc/2011-December/011070.html