Graham, On Monday 11 December 2006 14:24, Graham Leggett wrote: > Jason van Zyl wrote: > > Asking for a vote means that people can make preparations and actually > > figure out what's going to be done for the next release. Create a > > roadmap, field help and plan toward making something release worthy. > > When all that is done, the work has been looked over and it is felt that > > all the issues for the release have been dealt with then you call a > > vote. When it's actually ready. > > When I asked as the the status of the ear plugin last week, the answer > was that it was pretty much ready. I asked for a vote, but none came - > probably because people were busy this time of year, so being proactive > and knowing the drill I called the vote for the release, a perfectly > reasonable thing to do.
Part of the reason is that right now, the maven team CANNOT do a release based on the code in the tree. On Nov 1, the Apache requirements for a release "changed" and the Maven team (in particular Jason and Joakim) have been busy writing new plugins that would allow them to actually perform releases based on the new requirements. Until those plugins are ready and released, there is not really any point in calling other votes as releases couldn't be made anyway (they would need to be vetoed on legal grounds). That's probably one reason the vote never came. Another reason may be that no-one with commit access has time to do the release. Releasing requires a release manager to do the release. If no-one with commit access has time to do it, you can ask/vote all you want, but it won't be done. That all said, the required plugins should be released "shortly" at which point releases of the other plugins could be started, if someone steps up to actually do it. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
