On 7/24/01 1:13 PM, "[EMAIL PROTECTED]" <[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
+1
There is just no getting around the fact that some of the code in
a 2.1 app can not be adaptered in 3.0. I think it is acceptable to
change the API (actually we're just forming one) over major version
changes.
> 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]
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
