I think A is the proper way to go. Although it does not make sense for
someone to upgrade from 2.1 to 2.2 if there are not many bugfixes in the
2.2 release. It provides a clearer start point for those just starting
an application.
But B is easier on developers (of turbine) as there is less porting of
bugfixes across branches.
So I will live with either one.
john mcnally
[EMAIL PROTECTED] wrote:
>
> situation:
> there are many bug-fixes in cvs which should land in a 2.x release.
> on the other hand some stuff (castor, freemarker, ...) should be deprecated in
> 2.x to follow our deprecation rules (or we must add all the stuff to 3.0 :-( )
>
> options:
> A) a 2.1.1 release with all the bug-fixes without deprecation + a 2.2 release
> with deprecations (doesn't make sense, does it??)
>
> B) a 2.2 release with bugfixes + deprecations
> there will be no api changes in 2.2 only deprecations -> all 2.1 apps would work
> fine, but their might be some warnings at compile time
>
> i'll be on vacation from 4. - 17. august and i would like to have a 2.x release
> before my vacation.
>
> PLEASE VOTE!!
>
> martin
>
> ps: my vote A +0, B +1
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
