Mailing-List: contact etch-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: etch-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of sccomer@cisco.com designates
 64.102.122.148 as permitted sender)
Message-ID: <497E16DA.1000804@cisco.com>
Date: Mon, 26 Jan 2009 14:02:34 -0600
From: "scott comer (sccomer)" <sccomer@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: etch-dev@incubator.apache.org
Subject: Re: Voting...
References: <caf30e2a0901260957r109a5fecxad8f8618313c5921@mail.gmail.com>
In-Reply-To: <caf30e2a0901260957r109a5fecxad8f8618313c5921@mail.gmail.com>
Content-Type: multipart/mixed;
 boundary="------------020508040906050208010307"

--------------020508040906050208010307
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

so, how do you see that working. i have etch-31, i'm wanting to put that 
in the release.

do i just say, i wanna put this in the release invite discussion and 
while that's going on
i do it?

scott out

Niclas Hedhman wrote:
> Guys,
> I have a feeling that "too much" voting is going on... Typically we
> run "consensus" in Apache projects, i.e. someone makes a suggestion
> for changes or actions, and if people object they yell, otherwise
> proceed. For code changes, typically that means that the 'proposer' go
> ahead and make the changes, and if objections shows up and resolved to
> not make the change, then that is reversed. This has been coined CTR
> (Commit-Then-Review). Httpd project and others, run a RTC format for
> stable branches, but the vast majority uses the CTR model (incl httpd
> during 'new heavy development').
>
> So, the only 'requirement' for proper voting is Releases (well, some
> community issues as well, but...), which is a legal act and must be
> done properly.
>
> Cheers
> Niclas
>   

--------------020508040906050208010307--