RE: [RESULT][VOTE] - Allow RC votes to carry over at any point in the release process

2014-12-09 Thread Kessler CTR Mark J
+1 -Mark -Original Message- From: Harbs [mailto:harbs.li...@gmail.com] Sent: Tuesday, December 09, 2014 2:57 AM To: dev@flex.apache.org Subject: Re: [RESULT][VOTE] - Allow RC votes to carry over at any point in the release process Alright. I just removed the entire line. It jives with

Re: [RESULT][VOTE] - Allow RC votes to carry over at any point in the release process

2014-12-09 Thread OmPrakash Muppirala
On Dec 8, 2014 11:59 PM, "Harbs" wrote: > > Alright. I just removed the entire line. It jives with what Bertrand suggested anyways. > > Let’s try to avoid “carried votes” and just go with simplified revoting… > > From my perspective we’ve spent more than enough time on a really insignificant issue

Re: [RESULT][VOTE] - Allow RC votes to carry over at any point in the release process

2014-12-08 Thread Harbs
Alright. I just removed the entire line. It jives with what Bertrand suggested anyways. Let’s try to avoid “carried votes” and just go with simplified revoting… From my perspective we’ve spent more than enough time on a really insignificant issue. On Dec 9, 2014, at 9:45 AM, Alex Harui wrote:

Re: [RESULT][VOTE] - Allow RC votes to carry over at any point in the release process

2014-12-08 Thread Alex Harui
Crud, Unfortunately, I didn’t like either offering. It can’t be the “same” due diligence since the requestor didn’t examine the current artifacts. I say we either: 1) remove it entirely. This simplifies the guidelines but may complicate a situation where we don’t have enough voters with enough

Re: [RESULT][VOTE] - Allow RC votes to carry over at any point in the release process

2014-12-08 Thread Harbs
It looks fine to me. On Dec 9, 2014, at 9:11 AM, Erik de Bruin wrote: > I had to read the 'oversight' line twice to catch it's meaning. I have > suggested an alternative, please take a look. > > EdB > > > > On Tue, Dec 9, 2014 at 7:58 AM, Harbs wrote: >> Done. I added a sentence defining “c

Re: [RESULT][VOTE] - Allow RC votes to carry over at any point in the release process

2014-12-08 Thread Erik de Bruin
I had to read the 'oversight' line twice to catch it's meaning. I have suggested an alternative, please take a look. EdB On Tue, Dec 9, 2014 at 7:58 AM, Harbs wrote: > Done. I added a sentence defining “carrying” as “oversight”. > > On Dec 9, 2014, at 2:18 AM, Alex Harui wrote: > >> Maybe I’m

Re: [RESULT][VOTE] - Allow RC votes to carry over at any point in the release process

2014-12-08 Thread Harbs
Done. I added a sentence defining “carrying” as “oversight”. On Dec 9, 2014, at 2:18 AM, Alex Harui wrote: > Maybe I’m being too picky, but the vote proposal said: "I suggest that at > any point in the release process a vote should be carried over if the > person voting indicates they wish the v

Re: [RESULT][VOTE] - Allow RC votes to carry over at any point in the release process

2014-12-08 Thread Erik de Bruin
Agreed. We need broad language that represents the idea, not legalese that tries to capture all eventuallities. I'll make some modifications to the wiki if nobody beats me to it. Before we get into too long a discussion, please remember this is pretty much obsolete with the new voting guidelines.

Re: [RESULT][VOTE] - Allow RC votes to carry over at any point in the release process

2014-12-08 Thread Alex Harui
Maybe I’m being too picky, but the vote proposal said: "I suggest that at any point in the release process a vote should be carried over if the person voting indicates they wish the vote should carry over.” The current wiki version says: "The release manager can carry over of votes from previous r

Re: [RESULT][VOTE] - Allow RC votes to carry over at any point in the release process

2014-12-08 Thread Harbs
I don’t see my last two emails in the archives. Sorry if this is going out more than once… Here is a link to the modified wiki.[1] I think the changes are pretty minor… I removed mention of carried votes from the voting timeframe section, and clarified the wording in the “Product Release” secti

Re: [RESULT][VOTE] - Allow RC votes to carry over at any point in the release process

2014-12-08 Thread Harbs
That’s odd. I added [Result] to the subject when I sent it… Anyway, thanks. On Dec 9, 2014, at 12:04 AM, Erik de Bruin wrote: > Raising visibility :-) > > -- Forwarded message -- > From: *Harbs* > Date: Monday, December 8, 2014 > Subject: [VOTE] Allow RC votes to carry over at

Re: [RESULT][VOTE] Allow RC votes to carry over at any point in the release process

2014-12-08 Thread Harbs
Here is a link to the modified wiki.[1] I think the changes are pretty minor… I removed mention of carried votes from the voting timeframe section, and clarified the wording in the “Product Release” section. Harbs [1]https://cwiki.apache.org/confluence/display/FLEX/Guidelines

[RESULT][VOTE] - Allow RC votes to carry over at any point in the release process

2014-12-08 Thread Erik de Bruin
Raising visibility :-) -- Forwarded message -- From: *Harbs* Date: Monday, December 8, 2014 Subject: [VOTE] Allow RC votes to carry over at any point in the release process To: "dev@flex.apache.org" This vote passed with 6 +1 binding votes and one -1 binding votes. This vote i

[RESULT][VOTE] Allow RC votes to carry over at any point in the release process

2014-12-08 Thread Harbs
This vote passed with 6 +1 binding votes and one -1 binding votes. This vote is somewhat moot in light of the recent discussions and clarifications of what different people mean by “carried votes”, but I will edit the guidelines shortly to reflect what I believe was the spirit of the vote. If a