You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Randy Terbush <ra...@dsndata.com> on 1995/03/21 20:14:17 UTC

Re: vote counting.

I can't resist adding my 2 cents here...

One problem I see with the voting/release setup is that
there are too many intertwined changes to vote separately on.

I propose the following.

On hyperreal:

apache-lastrelease	/* Publically available server code */

apache-nextrelease	/* Working source tree */

incoming-patches	/* Weekly collection of patches */

official-patches	/* patches created on ~weekly basis */
			/* these would be based on apache-lastrelease */


Someone with ultimate decision about what patches to apply from the
incoming-patches would apply these to the source in apache-nextrelease.
A patch would be made weekly against the apache-lastrelease tree
and offered for group review and voting over the following week.
This would reduce the patches to vote on to one.  Changes could
then be offered throughout the voting period to fix problems in the
patch being voted on.  After the group is satisfied that this patch
is ready for prime time, we would update the lastrelease tree and
start the process again.

I think that the incoming directory should only be accessible by
members of the development group.  For the impatient ones, they
could be adding these to their own source tree.


OK.  I'll be quiet now.....