Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: 
 <CA+RK=_A9nS8pM-JPz+H7iVry_3ACotjMeg4EjfUTKJdFu1YZ5Q@mail.gmail.com>
References: 
 <CAPQV63WYwVFrvNsCoS28oMXiib+KT+79ZpJ9X35v5us0u7AtWg@mail.gmail.com>
 <CALte62zqoehSUnsLhFjPc13UHFM6FF69Y3-m2d2dpiuGOqZSmw@mail.gmail.com>
 <CA+RK=_DB+j1LuwR0W+D1JLvPKrtwXhwdYj1ve0GnNEDWypsewQ@mail.gmail.com>
 <CAPQV63VwjJxjkRDh__gJJd22xvCnjS62CNqGJWBKuQaEjMsAXg@mail.gmail.com>
 <CA+RK=_BaH7Wv8D+czV4U98ksRXhiTPoGch8TBLwt0ZKDBApCZA@mail.gmail.com>
 <CA+RK=_AKWnqQZRK_zRV5gKKzfp_Fr23Rxut46qQQZYgUSHYYJQ@mail.gmail.com>
 <CADcMMgHfZ4MBt8909ks-yOQE-5SdE8xmwMRTQz1WWiToO7TeNA@mail.gmail.com>
 <CA+RK=_AfF21NWB7HhiuMWMGO9W87Ao3y+io9cKtj=wt24TrGyA@mail.gmail.com>
 <CA+RK=_A7k6bqV8yzDgcfYKktJYzV9pcxZVRgjY6PqNJgYV2Kdg@mail.gmail.com>
 <CAPQV63Xv-am7rdW++G3ixZhYNuzyK79=tChB36e-vqJJZrnDxA@mail.gmail.com>
 <CA+RK=_A9nS8pM-JPz+H7iVry_3ACotjMeg4EjfUTKJdFu1YZ5Q@mail.gmail.com>
From: Jean-Marc Spaggiari <jean-marc@spaggiari.org>
Date: Wed, 18 Dec 2013 20:26:42 -0500
Message-ID: 
 <CAPQV63WA_U50wRzkuF1s_=6crJxwf=2u7D0wz5DHOJ_MPwjJ6A@mail.gmail.com>
Subject: Re: HBASE-7088 ready to commit ;)
To: dev <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=089e011846ee06d97b04edd90f8b

--089e011846ee06d97b04edd90f8b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

My point is that it forces more eyes to look at what is done and might
allow (force) more discussions?

On your side Andrew, regarding 0.98, can you please commit on not taking
any vacations for the next 12 months please? ;)


2013/12/18 Andrew Purtell <apurtell@apache.org>

> I don't see how more votes will increase the quality of design. Your
> participation in the community and providing of feedback will increase th=
e
> quality of design, and code too if you volunteer time to do code review o=
n
> JIRAs and reviews.apache.org.
>
> I can understand the motivation of adding friction. We already provide
> substantial friction as part of the normal Apache process of having Relea=
se
> Managers. If LarsH or Stack go away for a month, we probably won't have
> commits to 0.94 or 0.96 during that time. I'm not convinced we need more
> friction than this so I'm not in favor of the policy as it is currently
> written in the online manual. That said, I certainly have an open mind
> about this subject. Perhaps there is some evidence that more friction is
> warranted?
>
>
> On Wed, Dec 18, 2013 at 4:59 PM, Jean-Marc Spaggiari <
> jean-marc@spaggiari.org> wrote:
>
> > Honestly I'm pretty fine with the policy described at
> > http://hbase.apache.org/book.html#decisions
> >
> > "Patches that fit within the scope of a single Apache HBase component
> > require, at least, a +1 by one of the component's owners before commit.
> If
> > owners are absent -- busy or otherwise -- two +1s by non-owners will
> > suffice. " that mean usually one +1 is enough, or sometime 2x +1.
> >
> > But I will not complain if I need just one +1 for this patch ;)
> >
> > I think having 2x +1 will increase the quality of the code/design.
> >
> >
> >
> > 2013/12/18 Andrew Purtell <apurtell@apache.org>
> >
> > > Also let me clarify something: A while back we discussed the Hadoop
> > policy
> > > of requiring 3 +1s for a branch merge. That sounds reasonable to me. =
I
> > > don't see this in the current online manual text.
> > >
> > >
> > > On Wed, Dec 18, 2013 at 4:47 PM, Andrew Purtell <apurtell@apache.org>
> > > wrote:
> > >
> > > > Eh, that must have been discussed when I wasn't there or on the pho=
ne
> > and
> > > > unable to hear clearly. I'm not in favor of that policy as stated.
> > > > Ownership isn't working out as far as I can see. Owners are not
> around
> > > > enough. In fact I would say many people are relatively absent from
> the
> > > > community for long stretches of time. That's fine, this is a
> volunteer
> > > > society. We can't gate on an owner +1. I am not in favor of requiri=
ng
> > > more
> > > > than one +1 except for the obvious case where a committer should no=
t
> +1
> > > and
> > > > commit their own work. I am in favor of continuing our informal
> policy
> > of
> > > > CTR for trivial changes.
> > > >
> > > >
> > > >
> > > >
> > > > On Wed, Dec 18, 2013 at 4:42 PM, Stack <stack@duboce.net> wrote:
> > > >
> > > >> Here is what we decided as 'policy' on +1s:
> > > >>
> > > >> http://hbase.apache.org/book.html#decisions
> > > >>
> > > >> At our last meetup, we talked of upping the commit friction some t=
o
> > give
> > > >> chance for more review before commit but this suggestion did not
> > > progress
> > > >> beyond discussion.
> > > >>
> > > >> St.Ack
> > > >>
> > > >>
> > > >> On Wed, Dec 18, 2013 at 3:32 PM, Andrew Purtell <
> apurtell@apache.org>
> > > >> wrote:
> > > >>
> > > >> > AFAIK, we just don't want a committer to +1 their own work.
> > > >> >
> > > >> >
> > > >> > On Wed, Dec 18, 2013 at 3:30 PM, Andrew Purtell <
> > apurtell@apache.org>
> > > >> > wrote:
> > > >> >
> > > >> > > No
> > > >> > >
> > > >> > >
> > > >> > > On Wed, Dec 18, 2013 at 3:27 PM, Jean-Marc Spaggiari <
> > > >> > > jean-marc@spaggiari.org> wrote:
> > > >> > >
> > > >> > >> Don't we need 2 commiters  +1 per JIRA?
> > > >> > >>  Le 2013-12-18 18:23, "Andrew Purtell" <apurtell@apache.org> =
a
> > > >> =C3=A9crit :
> > > >> > >>
> > > >> > >> > Why is one +1 not good enough for commit?
> > > >> > >> >
> > > >> > >> >
> > > >> > >> > On Wed, Dec 18, 2013 at 12:38 PM, Ted Yu <
> yuzhihong@gmail.com>
> > > >> wrote:
> > > >> > >> >
> > > >> > >> > > I gave +1 already
> > > >> > >> > >
> > > >> > >> > > Waiting for an extra +1
> > > >> > >> > >
> > > >> > >> > >
> > > >> > >> > > On Wed, Dec 18, 2013 at 11:52 AM, Jean-Marc Spaggiari <
> > > >> > >> > > jean-marc@spaggiari.org> wrote:
> > > >> > >> > >
> > > >> > >> > > > It's small and there for a while.
> > > >> > >> > > >
> > > >> > >> > > > Thanks.
> > > >> > >> > > >
> > > >> > >> > >
> > > >> > >> >
> > > >> > >> >
> > > >> > >> >
> > > >> > >> > --
> > > >> > >> > Best regards,
> > > >> > >> >
> > > >> > >> >    - Andy
> > > >> > >> >
> > > >> > >> > Problems worthy of attack prove their worth by hitting back=
.
> -
> > > Piet
> > > >> > Hein
> > > >> > >> > (via Tom White)
> > > >> > >> >
> > > >> > >>
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > Best regards,
> > > >> > >
> > > >> > >    - Andy
> > > >> > >
> > > >> > > Problems worthy of attack prove their worth by hitting back. -
> > Piet
> > > >> Hein
> > > >> > > (via Tom White)
> > > >> > >
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Best regards,
> > > >> >
> > > >> >    - Andy
> > > >> >
> > > >> > Problems worthy of attack prove their worth by hitting back. -
> Piet
> > > Hein
> > > >> > (via Tom White)
> > > >> >
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > >
> > > >    - Andy
> > > >
> > > > Problems worthy of attack prove their worth by hitting back. - Piet
> > Hein
> > > > (via Tom White)
> > > >
> > >
> > >
> > >
> > > --
> > > Best regards,
> > >
> > >    - Andy
> > >
> > > Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> > > (via Tom White)
> > >
> >
>
>
>
> --
> Best regards,
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

--089e011846ee06d97b04edd90f8b--