[TYPO3-core] RFC: version numbers

Martin Kutschker Martin.Kutschker at blackbox.net
Wed Jan 4 09:33:07 CET 2006


Michael Stucki <michael at typo3.org> writes on 
Tue, 03 Jan 2006 19:14:11 +0100 (MET):

> Hi Robert,
> 
> > On Thursday 29 December 2005 17:29, Michael Stucki wrote:
> > 
> > > > Please make sure that the version number in the emconf is at
> > > > least
> > > > the version in TER when you commit to CVS. What I did with
> > > > TemplaVoila was setting it (manually) to 0.5.0CVS. But don't
> > > > add a
> > > > suffix like I did ("CVS"), "0.5.0" would have been better.
> > >
> > > Maybe this is again the reason why system extensions should not
> > > go into
> > > TER. If you still add it, you have to deal with the consequences
> > > on
> > > your own.
> > 
> > Sorry, but I don't agree. Let's take the TYPO3 core as an example.
> > Whenever we start working on the next version, we increase the
> > version
> > number in the CVS version to x.0.0dev. So what's wrong with doing
> > the same
> > with our system extensions?
> 
> We can increase that version number, but still it can lead to problems
> if people fetch e.g. tstemplate which was made for TYPO3 4.0 but use
> it with 3.8. It will not work correctly because of a change I've made
> recently!


If the extmgm would honour the TYPO3 version that comes with ext_emconf.php the would be no problems.


> I just don't see the sense in publishing _all_ system extensions
> without checking if they work. Plus, there is no need for people to
> get the 4.0 tstemplate in 3.8 because the feature is 4.0 specific!


I like the idea that sys exts are upgraded regularly and not only when a new TYPO3 is shipped.

Waiting a year for an new TYPO3 just to get a simple fix in TV sucks.

Masi 



More information about the TYPO3-team-core mailing list