[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??)
>
+1, I think this does make sense and follows the current deprecation
policy as I read it. This way, people will get their bug fixes as well
as get warnings that things are deprecated so that when they are gone in
3.0, there are no complaints.
This doesn't mean that these releases can't come closely after one
another since it would make sense to get them both out the door as
quickly as possible.
> 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, for the main reason that combining these will add confusion IMO.
josh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
