Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of neha.narkhede@gmail.com
 designates 209.85.220.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4ED58821.8080404@rowe-clan.net>
References: 
 <CAOG_4QagvkLNwYV1m-d8N=Th5C91JHm9TP6-x5dCeUobiuja4g@mail.gmail.com>
	<4ED58685.9000500@rowe-clan.net>
	<4ED58821.8080404@rowe-clan.net>
Date: Tue, 29 Nov 2011 17:50:52 -0800
Message-ID: 
 <CAOG_4QZ610LFeu1ARU4cfbw0uNW2mFB9TDF4DMcbzHvnzw=9mQ@mail.gmail.com>
Subject: Re: Voting time period can be shortened ? (was: [VOTE] Release Kafka
 0.7.0-incubating)
From: Neha Narkhede <neha.narkhede@gmail.com>
To: general@incubator.apache.org
Content-Type: multipart/alternative; boundary=bcaec54ee60e45389504b2e9f7d0

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

So, you are saying option 2 is a reasonable choice, given that only the
NOTICE/LICENSE files have changed one line here and there ?

Thanks,
Neha


On Tue, Nov 29, 2011 at 5:34 PM, William A. Rowe Jr. <wrowe@rowe-clan.net>wrote:

> On 11/29/2011 7:27 PM, William A. Rowe Jr. wrote:
>
>> On 11/29/2011 4:00 PM, Neha Narkhede wrote:
>>
>>>
>>> We would like to know if it is OK to either -
>>>
>>> 1. shorten the release VOTE for change to one non-code file
>>> 2. run 72 hour vote in parallel on the dev list as well as on general@
>>>
>>
>> I've never seen a point to 2) to running serial votes. You need only 3
>> +1's (more +1's than -1's)... usually three mentors are enough to finish
>> amoung the dev@ list, but announcing the vote (and its conclusion) on the
>> general@ list seems entirely appropriate. If folks at general@ would
>> like to have more input on the release, the ppmc dev@ list is really the
>> best place to get involved.
>>
>> It is important to always allow 72 full hours. The reason is simple, we
>> have participants in nearly every timezone, people who are here only on
>> their own time, and more people who are here almost exclusively on work
>> hours. 72 hours is long enough to accommodate them all, if they care to
>> participate.
>>
>
> [... trackpad arguing with me over whether I was done ...]
>
> So as I previously pointed out; *if* the community is already familiar
> with the candidate, thoroughly reviewed it for that full 72 hours, then
> if the RM replied to "this file is broken" with "I'll fast-track only that
> fix and roll a final candidate with a shortened 24 hour final vote" should
> put everyone in the frame of mind to review the revised candidate.
>
> But you can't ever shorten the net review time below three days :)
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<general-unsubscribe@incubator.apache.org>
> For additional commands, e-mail: general-help@incubator.apache.**org<general-help@incubator.apache.org>
>
>

--bcaec54ee60e45389504b2e9f7d0--