[TYPO3-ect] lib/div & compatibility

[Benjamin Mack]

Hey all,

actually IMHO the best solution would be to integrate a stable version 
of this API into the core (extension "cms"). Because ext devs already 
have trouble to check which version of TYPO3 they are using 
(compatversion is helping here), but with the whole lib / div versioning 
mess it gets more complicated and ext devs would say "you can only use 
my ext with div2007 and TYPO3 4.1" --- this is just plainly wrong. We're 
trying to make it easier but actually we're making it more complicated. 
div2007 was released because the div wasn't stable yet, and unless div 
is not stable, it is not really useful IMHO.

Of course, people will complain that the development would be slower 
when integrated in the core, but it does not make sense to change the 
APIs of a MVC framework all the time (MVC isn't that complicated ;-)). A 
framework is there to be stable, so the logical step would be to 
finalize lib/div and then integrate it in 4.3.
The ext authors would only need to have a check if compatversion is 4.3 
and otherwise would need to require lib / div from TER.

greetings,
benni.
-SDG

Daniel Bruessler wrote:
> Hello Franz,
> 
> so the only solutions seems to be that we use special extensionkeys for 
> every release of the framework.
> 
> * first release (=SVN branch01): lib 01 + div 01
> * second release (=SVN branch02): lib 02 + div 02
> 
> Within a branch _NO change of the API_, just bugfix-updates.
> 
> And an alias for the current version: lib=lib02, div=div02 (we know this 
> from Linux. If you install "mysql" you get the latest version of mysql.
> 
> => No problem to have several release-versions in the same installation.
> 
> Better?
> 
> Cheers!
> Daniel