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.
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 am also a member, have been here for 6-7 years, helped many project migrate to the ASF, have volunteered more of my time, produced more code (probably should have documented it), and helped more people then a good majority at the ASF.
I'm sorry, I fail to see how "my contribution is bigger than theirs" could possibly contribute anything to this discussion.
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature