hive-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ashutosh Chauhan <hashut...@apache.org>
Subject Re: [DISCUSS] Proposed Changes to the Apache Hive Project Bylaws
Date Sun, 19 Jan 2014 19:49:38 GMT
I will echo Thejas's concern w.r.t  RC voting. Usually it takes 2-3 rounds
of RC and folks generally tend to vote towards end of cycle. So, if we
increase it to 7 days, we are looking at 21 days (in worst case) to get a
release out, which may not be what we want. So, for RC vote my suggestion
will be to stick with current 3-days voting period.

For other votes (like committers, branch merges etc.) I don't have much
preference, but there also 7-days looks excessive.

Thanks,
Ashutosh


On Fri, Dec 27, 2013 at 9:33 AM, Thejas Nair <thejas@hortonworks.com> wrote:

> The changes look good to me.
> Only concern I have is with the 7 days for release candidate voting.
> Based on my experience with releases, it often takes few cycles to get
> the candidate out, and people tend to vote closer to the end of the
> voting period. This can mean that it takes several weeks to get a
> release out. But this will not be so much of a problem as long as
> people don't wait for end of the voting period to vote, or if they
> look at the candidate branch even before the release candidate is out.
>
> Should we also include a provision for branch merges ? I think we
> should have a longer voting period for branch merges (3 days instead
> of 1?) and require 3 +1s (this part is also in the hadoop by-law ) .
>
>
> On Thu, Dec 26, 2013 at 7:08 PM, Carl Steinbach <cws@apache.org> wrote:
> > I think we should make several changes to the Apache Hive Project Bylaws.
> > The proposed changes are available for review here:
> >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=38568856
> >
> > Most of the changes were directly inspired by provisions found in the
> Apache
> > Hadoop Project Bylaws.
> >
> > Summary of proposed changes:
> >
> > * Add provisions for branch committers and speculative branches.
> >
> > * Define the responsibilities of a release manager.
> >
> > * PMC Chairs serve for one year and are elected by the PMC using Single
> > Transferable Vote (STV) voting.
> >
> > * With the exception of code change votes, the minimum length of all
> voting
> > periods is extended to seven days.
> >
> > Thanks.
> >
> > Carl
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Mime
View raw message