Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-22 Thread Jakob Homan
With 13 +1's from PMC members, the vote passes. I'll update the language and commit it to the documentation. -jg On Fri, Jul 15, 2011 at 9:18 AM, Owen O'Malley wrote: > > On Mon, Jul 11, 2011 at 5:11 PM, Jakob Homan wrote: >> As discussed in the recent thread on HDFS-1623 branching models, I'd

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-15 Thread Owen O'Malley
On Mon, Jul 11, 2011 at 5:11 PM, Jakob Homan wrote: > As discussed in the recent thread on HDFS-1623 branching models, I'd > like to amend the bylaws to provide that branches should get a minimum > of three committer +1s before being merged to trunk. +1

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-13 Thread Tom White
+1 Tom On Mon, Jul 11, 2011 at 5:11 PM, Jakob Homan wrote: > As discussed in the recent thread on HDFS-1623 branching models, I'd > like to amend the bylaws to provide that branches should get a minimum > of three committer +1s before being merged to trunk. > > The rationale: > Feature branches

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-13 Thread Nigel Daley
+1 Cheers, Nige On Jul 12, 2011, at 10:01 AM, Stack wrote: > +1 > > On Mon, Jul 11, 2011 at 5:41 PM, Eli Collins wrote: >> +1 Sounds good to me. >> >> Something like the following? >> >> Index: main/author/src/documentation/content/xdocs/bylaws.xml >>

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-13 Thread Tsz Wo Sze
+1. Tsz-Wo From: Stack To: general@hadoop.apache.org Sent: Tuesday, July 12, 2011 10:01 AM Subject: Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge +1 On Mon, Jul 11, 2011 at 5:41 PM, Eli Collins wrote: > +1   Sounds good to

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-12 Thread Stack
+1 On Mon, Jul 11, 2011 at 5:41 PM, Eli Collins wrote: > +1   Sounds good to me. > > Something like the following? > > Index: main/author/src/documentation/content/xdocs/bylaws.xml > == >             Lazy consensus of active committe

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-12 Thread Doug Cutting
On 07/11/2011 05:41 PM, Eli Collins wrote: > Index: main/author/src/documentation/content/xdocs/bylaws.xml > == > Lazy consensus of active committers, but with a minimum of > -one +1. The code can be committed

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-11 Thread Suresh Srinivas
+1 from me.

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-11 Thread Todd Lipcon
Sounds fine to me. +1 On Mon, Jul 11, 2011 at 9:30 PM, Mahadev Konar wrote: > +1 > > mahadev > > On Mon, Jul 11, 2011 at 9:26 PM, Arun C Murthy > wrote: > > +1 > > > > Arun > > > > On Jul 11, 2011, at 5:11 PM, Jakob Homan wrote: > > > >> As discussed in the recent thread on HDFS-1623 branching m

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-11 Thread Mahadev Konar
+1 mahadev On Mon, Jul 11, 2011 at 9:26 PM, Arun C Murthy wrote: > +1 > > Arun > > On Jul 11, 2011, at 5:11 PM, Jakob Homan wrote: > >> As discussed in the recent thread on HDFS-1623 branching models, I'd >> like to amend the bylaws to provide that branches should get a minimum >> of three commi

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-11 Thread Arun C Murthy
+1 Arun On Jul 11, 2011, at 5:11 PM, Jakob Homan wrote: > As discussed in the recent thread on HDFS-1623 branching models, I'd > like to amend the bylaws to provide that branches should get a minimum > of three committer +1s before being merged to trunk. > > The rationale: > Feature branches ar

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-11 Thread Dhruba Borthakur
+1 On Tue, Jul 12, 2011 at 12:56 AM, Aaron T. Myers wrote: > +1 from me as well. > > Thanks for running this vote, Jakob. > > Aaron > > On Jul 11, 2011, at 7:44 PM, Jakob Homan wrote: > > > +1 to Eli's wording. > > > > On Mon, Jul 11, 2011 at 5:41 PM, Eli Collins wrote: > >> +1 Sounds good t

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-11 Thread Aaron T. Myers
+1 from me as well. Thanks for running this vote, Jakob. Aaron On Jul 11, 2011, at 7:44 PM, Jakob Homan wrote: > +1 to Eli's wording. > > On Mon, Jul 11, 2011 at 5:41 PM, Eli Collins wrote: >> +1 Sounds good to me. >> >> Something like the following? >> >> Index: main/author/src/documen

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-11 Thread Jakob Homan
+1 to Eli's wording. On Mon, Jul 11, 2011 at 5:41 PM, Eli Collins wrote: > +1   Sounds good to me. > > Something like the following? > > Index: main/author/src/documentation/content/xdocs/bylaws.xml > == >             Lazy consensus

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-11 Thread Eli Collins
+1 Sounds good to me. Something like the following? Index: main/author/src/documentation/content/xdocs/bylaws.xml == Lazy consensus of active committers, but with a minimum of -one +1. The code can be commi

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-11 Thread Jakob Homan
That's certainly not the intention, although I note that the current +1 requirement on code changes would apparently allow a committer to +1 h{is,er} own patch: "A change made to a codebase of the project and committed by a committer. This includes source code, documentation, website content, etc.

Re: [VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-11 Thread Todd Lipcon
To clarify, is there any restriction on who may give the +1s? For example, if a branch has a group of 5 committers primarily authoring the patches, can the three +1s be made by a subset of those committers? -Todd On Mon, Jul 11, 2011 at 5:11 PM, Jakob Homan wrote: > As discussed in the recent t

[VOTE] Change bylaws to require 3 binding +1s for branch merge

2011-07-11 Thread Jakob Homan
As discussed in the recent thread on HDFS-1623 branching models, I'd like to amend the bylaws to provide that branches should get a minimum of three committer +1s before being merged to trunk. The rationale: Feature branches are often created in order that developers can iterate quickly without th