corinthia-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: [DISCUSS] [PRE-VOTE] Release candidate 0.1
Date Fri, 14 Aug 2015 19:04:03 GMT
During many [VOTE]s, people often give a -1 (if thought critical) and state the conditions
that will turn their vote into a +1.  That is one way the situation that Peter raises can
be handled.  

Note that while a -1 on a release [VOTE] is not a veto, the idea is that -1 votes are taken
seriously and addressed if possible.

 - Dennis

-----Original Message-----
From: Peter Kelly [] 
Sent: Friday, August 14, 2015 11:25
Subject: Re: [DISCUSS] [PRE-VOTE] Release candidate 0.1

> On 15 Aug 2015, at 1:11 am, Dennis E. Hamilton <> wrote:
> With regard to what release votes are supposed to reflect, pre-voting makes absolutely
no sense to me.  The ballots cast should follow a critical review of the *specific* release
> I have said all I need to say about this.

Maybe voting is not the best term to use for this period. The way I understood it was a chance
to hammer out last minute issues (like the line ending problem I just mentioned) and once
the all the issues I’ve found have been sorted out, I give my +1.

Keep in mind that release candidates differ slightly from other things we normally vote on,
because there’s sometimes obvious technical problems (code not compiling, tests failing)
that are not controversial, and are a matter of fixing and issuing a new release candidate.

If you have a suggestion for a less ambiguous term we could use so that individuals can express
the notion that all the problems they have found/care about have now been fixed, I would be
happy for us to change to using that term instead. What is the typical practice on other ASF

Dr Peter M. Kelly

PGP key: <>
(fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)

View raw message