On 18 Sep 07, at 9:22 AM 18 Sep 07, Mark Hobson wrote:

On 12/09/2007, Jason van Zyl <[EMAIL PROTECTED]> wrote:
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.

So are we agreed on a 2.0.8 release before making 2.0.x use
maven-artifact 3.x?  I'd like to change my stance and see 2.0.8
released ASAP since it is currently blocking a release of
maven-dependency-tree 1.1.  Are the remaining issues those in JIRA?
Any ETA for 2.0.8?


I think it makes sense to release 2.0.8 as is. When Herve comes back he can roll in his encoding changes. That will fix the biggies for 2.0.8, there's a couple things I will fix, anything else anyone wants to tackle and then we can release it. I think waiting for the encoding fixes is important. Aside from that I think we can push out most other things and release. Then attempt the maven-artifact integration.

Cheers,

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


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]

Reply via email to