On 11 Sep 07, at 10:13 AM 11 Sep 07, Carlos Sanchez wrote:
On 9/11/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 11 Sep 07, at 9:25 AM 11 Sep 07, Carlos Sanchez wrote:
i'd like to see 2.0.8 released with the old artifact code and then
2.0.9 with the new one so we have a clear checkpoint to easily
know if
there are problems with the new approach
How is 2.0.7 not a clear point?
I just would like to reduce the changes between releases. We release
what is now as 2.0.8 and then prepare artifact 3.0 for 2.0.9
if something breaks between 2.0.8 and 2.0.9 we know clearly it was the
artifact changes and it's just a matter of downgrading to 2.0.8. I
think it'd make our life easier
That sounds like a reasonable plan of action. It's the long term that
matters for maintenance. Another release with the old code has no
downside in the short term.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
