Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CA+96GG5pUnHmwE6qHTL_OENsTQdOwz8YPKmThJh3=89C2JjZtg@mail.gmail.com>
References: 
 <CAPaJBx5NQb_D4XO4wi+S2J8Jy5K9bGVe2AFm6F1JMH33A+r+dg@mail.gmail.com>
	<CA+96GG4EWANZrywOOnejwRNonvKn-3cCo56Bw_RLrnLdYM=KZQ@mail.gmail.com>
	<CAPaJBx6-Vd7TfUX+k9VAQ2_JkymV-r0CNv10kuoTHW4ZKi4ccA@mail.gmail.com>
	<CA+96GG74ATsXgOO1sTTTJb-9U34vzEKNMcf7cCh9+sLR86Q0=Q@mail.gmail.com>
	<CAPaJBx4+vBXpEC1zHmy7iFwYfcy4aQwLPa58caLZRr_8JXndeg@mail.gmail.com>
	<CA+96GG5pUnHmwE6qHTL_OENsTQdOwz8YPKmThJh3=89C2JjZtg@mail.gmail.com>
Date: Mon, 29 Oct 2012 15:17:35 +0000
Message-ID: 
 <CAPaJBx7wkpb7pve0OKSYOb-L-X0SPL9CKoj-TSnuG=ivfEL5vg@mail.gmail.com>
Subject: Re: Shipping binary file in CloudStack release
From: Noah Slater <nslater@apache.org>
To: general@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8ff24e1f5923d004cd342bb9

--e89a8ff24e1f5923d004cd342bb9
Content-Type: text/plain; charset=ISO-8859-1

On 29 October 2012 15:13, Chip Childers <chip.childers@sungard.com> wrote:

>
> I'll try to be more clear next time.  I'm holding the vote open
> specifically because of this outstanding question, *regardless* of the
> current tally.  That's what I was expressing.


Understood. I suspected we were on the same page, but I wanted to make sure.


> No disagreement.  Again, that's why I'm holding the vote open until we
> get enough clarity on the topic being discussed here.
>

Yep, and thank you. Especially considering the considerable delay in me
being able to find time to test.


> IMO, fixing this in the policy would include a statement about the RM
> having the right (but not the obligation) to abort the vote based on
> any individual issue raised by a voter.  But perhaps this is a topic
> for another list...
>
> Using this thread a specific example, I'll abort if the advice here is
> that waf needs to be removed in it's current form.
>

This may be an area for project bylaws.

On CouchDB, as the release manager, I added this to our release process:

"The release manager has the power to abort a vote at any point and for any
reason."

I advise we do the same for CloudStack.

Basically, as RM, as long as you're operating within the Apache framework
and principals, and there is a documented release policy that the community
(even tacitly) agrees with, then you are empowered to do whatever you want
within the limits of that.


-- 
NS

--e89a8ff24e1f5923d004cd342bb9--