On 1-Jul-09, at 10:52 AM, Paul Benedict wrote:
It's logical to believe that 2.1 and 2.2 contain almost all the
unresolved bugs of 2.0.x. Since 2.0.x is no longer being supported,
there's no good reason to keep them attached to that version. You only
want to backport the issues that will get fixing -- not potential
fixes UNLESS the issue is exclusively a 2.0.x issue.
Unfortunately this may not be the case because the code bases are now
pretty different. My only concern is that the 2.0.x line becomes the
ugly stepchild meanwhile this is where the vast majority of our users
live.
-- Paul
On Wed, Jul 1, 2009 at 12:38 PM, Jason van Zyl<[email protected]>
wrote:
You need to leave the bugs raised against 2.0.x because there is no
way
around the fact that 2.0.x is going to be the dominant version used
for
quite some time. We can't just stop bug fixing the 2.0.x line. If
you moved
them all how are you going to know what applies?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
