Hi Henning,

> The problem is, that many projects depend on
> non-released-more-or-less-arbitrary snapshots of the commons. And
> these are in part incompatible.
> 
> The release schedule of commons is unfortunately quite 
> "flexible", yep.
> 

I totally agree.

In both cases even the API does not seem to be stable, which is pretty
awfull, as you cannot rely on it. So I really beg everyone not to use
another stupid commons snapshot yet :).

And you are right - the commons stuff needs better defined release cycles to
avoid that problem in future.

I hope you choose a more stable versions - if ever avialable - of these commons stuff 
when you
release Turbine 2.4. 

BTW Any roadmap ideas? ;)

--
tobias rademacher
[sofwareentwickler]

innoWake gmbh
innovative.software.development();
graf-arco-strasse 18 | 89079 ulm-donautal
fon: +49 (0)7 31 - 5 50 27 - 0
fax: +49 (0)7 31 - 5 50 27 - 20
[EMAIL PROTECTED]
www.innowake.de

Diese E-Mail enth�lt vertrauliche und/oder
rechtlich gesch�tzte Informationen.
Wenn Sie nicht der richtige Adressat sind,
oder diese E-Mail irrt�mlich erhalten haben,
informieren Sie bitte sofort den Absender
und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser E-Mail ist nicht gestattet.

This e-mail may contain confidential and/or
privileged information. If you are not the
intended recipient (or have received this
e-mail in error) please notify the sender
immediately and destroy this e-mail. Any
unauthorised copying, disclosure or
distribution of the material in this e-mail
is strictly forbidden.






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to