Additional information:
The mojo-parent has been staged and is available on the following location: https://nexus.codehaus.org/content/repositories/orgcodehausmojo-016/org/codehaus/mojo/mojo-parent/25/ Some modifications had to be done on the mojo-parent, but they all concern the staging mechanism, so there's no reason to start a revote. - Robert From: [email protected] To: [email protected] Date: Mon, 6 Sep 2010 10:21:45 +0000 Subject: RE: [mojo-dev] [VOTE] Release Mojo Parent 25 Maybe I should have called for a vote only for the staging-support followed by the one for the mojo-parent. But these things are so much related to each other that I've decided to do it in one vote. I agree on the sanity check, but in this rare case I think it should happen after the vote has passed. But now that you bring this up: what will be the damage? Actually it's none. So I'll stage it as well :) - Robert Date: Mon, 6 Sep 2010 11:20:02 +0100 From: [email protected] To: [email protected] Subject: Re: [mojo-dev] [VOTE] Release Mojo Parent 25 I have to agree with Benjamin On 6 September 2010 10:56, Benjamin Bentmann <[email protected]> wrote: Robert Scholte wrote: I have thought about it, but it's some sort of chicken/egg problem to me. The vote on using staging is part of this release. I can't quite follow. Yes, this vote concerns the general release workflow for Mojo plugins, but how you personally attempt to release this particular parent POM is a different story to me. It's just that it looks odd to me. This parent is about selling the staging process to the community, yet itself doesn't use staging? Also, having the parent staged would provide a sanity check that all its configuraton is sound and fine for staging to actually work. Benjamin --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
