[TYPO3-ect] lib/div & compatibility

[philip.almeida at ippimail.com]

> Hello philip,
> 
>> Don't forget the
KickStarter, the
>> grow of several div's can make the
kickstarter development more
>> complicated.
> 
> Yes the kickstarter - we need to find a solutions for it.
>
>> This kind of evolution of the API (separated by Year)
>> is a new thing that you do not see elsewhere (as I Know).
> 
> In my eyes the yearly versioning is _not_ needed.
It's very strange to
> have such kind of versioning.
>
>> I am not going to develop
>>
div2008__extjswidgets (...)
> 
> No :-) you write an
extension and put "lib02" and "div02"
>
Imagine that you just set the dependency "lib02" and
"div02" and get the
> 2nd public release of lib/div (if
we decide to do it that way). 02 would
> be the second release for
public usage. The next release would be
> "lib03" and
"div03".
> 
> => So several versions of
lib/div can be in the same TYPO3-installation.
Hi
Daniel..., 
..yes, I see your "vision", but is there a
real need for that kind of aproach?
The software products we see do
not follow that rule, they all have one name lot's of
versions.
Should not we sustain the backward compatibility in the
API itself rather then in multiple distributions of the same
product? 
Is there any advantage on going that away for future
developers, forgetting that there are already some existing extensions
developed on it?
 
Best regards,
Philip
Almeida 
> 
> Cheers!
> Daniel
>> Philip Almeida
>> Einstein "Make things easy
but
>> not easier, make  things simple but not
simplier"
>
_______________________________________________
>
TYPO3-team-extension-coordination mailing list
>
TYPO3-team-extension-coordination at lists.netfielders.de
>
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination
> 
Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com/