On 12/12/2006, at 6:24 AM, Graham Leggett wrote:
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.
Sorry, but no, it's not. Votes can only be sensibly taken on code that is ready to be released right now. As others have pointed out, there were still changes to be made, and you need someone actually able to cut the release.
It's entirely appropriate for you to call for a discussion on a release to get things moving. It's entirely appropriate for you to cast your vote on a release that you have tested and think is ready.
Calling for a vote is basically saying "DO IT NOW", which if you aren't the one intending to be the one do it comes off as pretty rude. That's why you got the response you did, and I expect I'd get the same if I tried it over at apr or httpd.
Of course, don't let that stop you from contributing here in the future.
The reason for the call for a vote is that right now the snapshot docs for the plugins are currently live in the maven documentation tree. Fixing this either means taking the docs down, or simply making releases of the plugins in question. Making releases is a step forward IMHO and a far better solution than taking the docs down.
I don't understand this. Is there a field in the documentation that is only available in the snapshot and not documented as such? We don't maintain separate versions of the documentation (to allow us to make improvements to it that are relevant to old versions as well), instead opting to outline when new things were introduced. If they haven't been, that's a bug that should be fixed.
Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
