On Sep 21, 2007, at 2:46 PM, William A. Rowe, Jr. wrote:
Jim Jagielski wrote:
So how about this... this is something that has been done, and
is being done, in just about every ASF project. Why don't
we vote on this and give it a time-table at which point we
review how it's worked out over the last 3 months or so
and fine-tune if and as needed?
Once we agree this is a workable implementation, we can
determine numbering aspects and initial code repo loads.
There's a confusing aspect; what if the new proposed process/policies
get dropping to a /dev/howitworks.html sort of document, and that
entire document is voted on?
My point is that its not really new, but rather based
on what other projects are doing. The only "new" part
would be the requirement that API changes require advanced
notice and, by default, are lazy consensus. Of course
this would be for trunk, since API changes on release
branches would be normal RTC rules anyway...
http://www.apache.org/foundation/voting.html
Trunk and development branches are just SVN best practices.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
