No you do not need to vote on bugs in the bug list. These items are determined by "lazy consensus" -- meaning you commit and if no one notices/objects then they all agree ;-). As for whether backward compatible changes must be voted on, this is a matter for your community to decide in my opinion. If you feel this is important then propose some kind of policy and vote to adopt it.I'm hoping Dion and Oliver (our new friends at Jakarta) will be able to = help with the exact process. To be honest, I haven't been able to = determine (from the documentation) the exact granularity of an action = item. For instance, I doubt we'd need to vote on whether to fix bugs in = the bug list ... but what if the fix causes a non-backwards compatible = change?
One thing I recommend (just a suggestion) is that you document important decisions that are "timeless" for example if you decide to require all sources must use javadoc for public and protected methods to be committed. Propose that as a requirement and then vote it, and document it on the site somewhere noting when it was voted, perhaps links to the archive, etc. Otherwise you'll rehash issues over and over again.
Note that ANYONE can vote. But only committer votes are "binding".
PROPOSAL:The Tapestry community should immediately adopt the voting meritocracy = guidelines of the Apache project, as detailed in http://jakarta.apache.org/site/guidelines.html. VOTES: Howard Lewis Ship: +1 Mind Bridge: Malcolm Edgar: Richard Lewis-Shell: ---- Howard Lewis Ship [EMAIL PROTECTED] http://tapestry.sf.net
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
