[TYPO3-ect] lib/div & compatibility

[Daniel Bruessler]

Hello Franz,

>> An additional function _is_ an API-change :-)
>> Example: If lib02 and div03 are the current extensionkeys and they are
>> in use for some extensions any new functions should go into a new branch
>> lib03 and div03. Just bugfixes for already existing functions go in
>> lib02 and div02.

If you're the main-maintainer of div & lib it's easy for you to put 
everything in the newest version of div & lib. You can always use the 
current one in extensions like tt_products .

For others who want to use how it is (e.g. I'm one of this group) it's 
good to have a defined version with a non-changing API. For example 
"lib02" and "div02".

The alias: Please see the extension "ect". That is an 
"extension-package". In our case we just have ONE extension in the package.

Clear now what I mean?

Cheers!
Daniel

> This is bad. Imagine you are developing for div02 and then you want to
> add a new function. Then this is so restrictive that you cannot continue
> and must move to div03 which will take many months to get ready.
> Or you must copy this code into all of your extensions. This is also bad.
> This is only managable if div02 is already in RC phase. But it is too
> restrictive during alpha and beta phase.
> - Franz