You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by Matt Foley <ma...@apache.org> on 2013/05/21 23:10:29 UTC
[PROPOSAL] change in bylaws to remove Release Plan vote
Hi all,
This has been a side topic in several email threads recently. Currently we
have an ambiguity. We have a tradition in the dev community that any
committer can create a branch, and propose release candidates from it. Yet
the Hadoop bylaws say that releases have to be planned in advance, the plan
needs to be voted on, and presumably can be denied.
Apache policies (primarily here <http://www.apache.org/dev/release.html>
and here <http://www.apache.org/foundation/voting.html>, with
non-normative commentary
here<http://incubator.apache.org/guides/releasemanagement.html#best-practice>)
are very clear on how Releases have to be approved, and our bylaws are
consistent with those policies. But Apache policies don't say anything
I've found about Release Plans, nor about voting on Release Plans.
I propose the following change, to remove Release Plan votes, and give a
simple definition of Release Manager role. I'm opening discussion with
this proposal, and will put it to a vote if we seem to be getting
consensus. Here's the changes I suggest in the
Bylaws<http://hadoop.apache.org/bylaws.html>
document:
===
1. In the "Decision Making" : "Actions" section of the Bylaws, the
following text is removed:
** Release Plan*
Defines the timetable and actions for a release. The plan also nominates a
Release Manager.
Lazy majority of active committers
2. In the "Roles and Responsibilities" section of the Bylaws, an additional
role is defined:
** Release Manager*
A Release Manager (RM) is a committer who volunteers to produce a Release
Candidate according to
HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
The RM shall publish a Release Plan on the *common-dev@* list stating the
branch from which they intend to make a Release Candidate, at least one
week before they do so. The RM is responsible for building consensus around
the content of the Release Candidate, in order to achieve a successful
Product Release vote.
===
Please share your views.
Best regards,
--Matt (long-time release manager)
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Arun C Murthy <ac...@hortonworks.com>.
+1, thanks for taking the initiative on this Matt.
On May 21, 2013, at 2:10 PM, Matt Foley wrote:
> Hi all,
> This has been a side topic in several email threads recently. Currently we
> have an ambiguity. We have a tradition in the dev community that any
> committer can create a branch, and propose release candidates from it. Yet
> the Hadoop bylaws say that releases have to be planned in advance, the plan
> needs to be voted on, and presumably can be denied.
>
> Apache policies (primarily here <http://www.apache.org/dev/release.html>
> and here <http://www.apache.org/foundation/voting.html>, with
> non-normative commentary
> here<http://incubator.apache.org/guides/releasemanagement.html#best-practice>)
> are very clear on how Releases have to be approved, and our bylaws are
> consistent with those policies. But Apache policies don't say anything
> I've found about Release Plans, nor about voting on Release Plans.
>
> I propose the following change, to remove Release Plan votes, and give a
> simple definition of Release Manager role. I'm opening discussion with
> this proposal, and will put it to a vote if we seem to be getting
> consensus. Here's the changes I suggest in the
> Bylaws<http://hadoop.apache.org/bylaws.html>
> document:
>
> ===
>
> 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> following text is removed:
>
> ** Release Plan*
>
> Defines the timetable and actions for a release. The plan also nominates a
> Release Manager.
>
> Lazy majority of active committers
>
>
> 2. In the "Roles and Responsibilities" section of the Bylaws, an additional
> role is defined:
>
> ** Release Manager*
>
> A Release Manager (RM) is a committer who volunteers to produce a Release
> Candidate according to
> HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> The RM shall publish a Release Plan on the *common-dev@* list stating the
> branch from which they intend to make a Release Candidate, at least one
> week before they do so. The RM is responsible for building consensus around
> the content of the Release Candidate, in order to achieve a successful
> Product Release vote.
>
> ===
>
> Please share your views.
> Best regards,
> --Matt (long-time release manager)
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Giridharan Kesavan <gk...@hortonworks.com>.
+1
-Giri
On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
> Hi all,
> This has been a side topic in several email threads recently. Currently we
> have an ambiguity. We have a tradition in the dev community that any
> committer can create a branch, and propose release candidates from it. Yet
> the Hadoop bylaws say that releases have to be planned in advance, the plan
> needs to be voted on, and presumably can be denied.
>
> Apache policies (primarily here <http://www.apache.org/dev/release.html>
> and here <http://www.apache.org/foundation/voting.html>, with
> non-normative commentary
> here<
> http://incubator.apache.org/guides/releasemanagement.html#best-practice>)
> are very clear on how Releases have to be approved, and our bylaws are
> consistent with those policies. But Apache policies don't say anything
> I've found about Release Plans, nor about voting on Release Plans.
>
> I propose the following change, to remove Release Plan votes, and give a
> simple definition of Release Manager role. I'm opening discussion with
> this proposal, and will put it to a vote if we seem to be getting
> consensus. Here's the changes I suggest in the
> Bylaws<http://hadoop.apache.org/bylaws.html>
> document:
>
> ===
>
> 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> following text is removed:
>
> ** Release Plan*
>
> Defines the timetable and actions for a release. The plan also nominates a
> Release Manager.
>
> Lazy majority of active committers
>
>
> 2. In the "Roles and Responsibilities" section of the Bylaws, an additional
> role is defined:
>
> ** Release Manager*
>
> A Release Manager (RM) is a committer who volunteers to produce a Release
> Candidate according to
> HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> The RM shall publish a Release Plan on the *common-dev@* list stating the
> branch from which they intend to make a Release Candidate, at least one
> week before they do so. The RM is responsible for building consensus around
> the content of the Release Candidate, in order to achieve a successful
> Product Release vote.
>
> ===
>
> Please share your views.
> Best regards,
> --Matt (long-time release manager)
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by "Aaron T. Myers" <at...@cloudera.com>.
+1
I've always found the Release Plan votes a bit bizarre, and the fact that
we've gone through many releases that did not have a corresponding Release
Plan vote suggest to me that we should just scrap them.
--
Aaron T. Myers
Software Engineer, Cloudera
On Tue, May 21, 2013 at 5:37 PM, Chris Douglas <cd...@apache.org> wrote:
> +1
>
> Thanks for taking care of this, Matt. -C
>
> On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
> > Hi all,
> > This has been a side topic in several email threads recently. Currently
> we
> > have an ambiguity. We have a tradition in the dev community that any
> > committer can create a branch, and propose release candidates from it.
> Yet
> > the Hadoop bylaws say that releases have to be planned in advance, the
> plan
> > needs to be voted on, and presumably can be denied.
> >
> > Apache policies (primarily here <http://www.apache.org/dev/release.html>
> > and here <http://www.apache.org/foundation/voting.html>, with
> > non-normative commentary
> > here<
> http://incubator.apache.org/guides/releasemanagement.html#best-practice>)
> > are very clear on how Releases have to be approved, and our bylaws are
> > consistent with those policies. But Apache policies don't say anything
> > I've found about Release Plans, nor about voting on Release Plans.
> >
> > I propose the following change, to remove Release Plan votes, and give a
> > simple definition of Release Manager role. I'm opening discussion with
> > this proposal, and will put it to a vote if we seem to be getting
> > consensus. Here's the changes I suggest in the
> > Bylaws<http://hadoop.apache.org/bylaws.html>
> > document:
> >
> > ===
> >
> > 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> > following text is removed:
> >
> > ** Release Plan*
> >
> > Defines the timetable and actions for a release. The plan also nominates
> a
> > Release Manager.
> >
> > Lazy majority of active committers
> >
> >
> > 2. In the "Roles and Responsibilities" section of the Bylaws, an
> additional
> > role is defined:
> >
> > ** Release Manager*
> >
> > A Release Manager (RM) is a committer who volunteers to produce a Release
> > Candidate according to
> > HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> > The RM shall publish a Release Plan on the *common-dev@* list stating
> the
> > branch from which they intend to make a Release Candidate, at least one
> > week before they do so. The RM is responsible for building consensus
> around
> > the content of the Release Candidate, in order to achieve a successful
> > Product Release vote.
> >
> > ===
> >
> > Please share your views.
> > Best regards,
> > --Matt (long-time release manager)
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Chris Douglas <cd...@apache.org>.
+1
Thanks for taking care of this, Matt. -C
On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
> Hi all,
> This has been a side topic in several email threads recently. Currently we
> have an ambiguity. We have a tradition in the dev community that any
> committer can create a branch, and propose release candidates from it. Yet
> the Hadoop bylaws say that releases have to be planned in advance, the plan
> needs to be voted on, and presumably can be denied.
>
> Apache policies (primarily here <http://www.apache.org/dev/release.html>
> and here <http://www.apache.org/foundation/voting.html>, with
> non-normative commentary
> here<http://incubator.apache.org/guides/releasemanagement.html#best-practice>)
> are very clear on how Releases have to be approved, and our bylaws are
> consistent with those policies. But Apache policies don't say anything
> I've found about Release Plans, nor about voting on Release Plans.
>
> I propose the following change, to remove Release Plan votes, and give a
> simple definition of Release Manager role. I'm opening discussion with
> this proposal, and will put it to a vote if we seem to be getting
> consensus. Here's the changes I suggest in the
> Bylaws<http://hadoop.apache.org/bylaws.html>
> document:
>
> ===
>
> 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> following text is removed:
>
> ** Release Plan*
>
> Defines the timetable and actions for a release. The plan also nominates a
> Release Manager.
>
> Lazy majority of active committers
>
>
> 2. In the "Roles and Responsibilities" section of the Bylaws, an additional
> role is defined:
>
> ** Release Manager*
>
> A Release Manager (RM) is a committer who volunteers to produce a Release
> Candidate according to
> HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> The RM shall publish a Release Plan on the *common-dev@* list stating the
> branch from which they intend to make a Release Candidate, at least one
> week before they do so. The RM is responsible for building consensus around
> the content of the Release Candidate, in order to achieve a successful
> Product Release vote.
>
> ===
>
> Please share your views.
> Best regards,
> --Matt (long-time release manager)
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Matt Foley <ma...@apache.org>.
Hi Konstantin,
The amendment I've proposed actually leaves the Release Plan in place. In
fact, where one could say the current bylaws don't require a Release Plan
for every release, this amendment makes clear that it does. It just
doesn't have to be voted on.
I would think that a controversial release plan would generate discussion,
which would give guidance to the prospective RM about what he or she needs
to do in order to achieve enough consensus to pass a Product Release vote.
There's no need to vote on intentions, tho. If people don't like the
release (as planned and/or as delivered) they can vote down the RC, which
is a concrete artifact.
I'm not concerned that people won't comment until the RC comes out. Folks
around here are pretty free with their opinions :-) And release votes are
majority vote, so there are no vetoes, and "submarine" behavior doesn't get
rewarded.
--Matt
On Wed, May 22, 2013 at 11:20 AM, Konstantin Shvachko
<sh...@gmail.com>wrote:
> Couldn't reply yesterday.
> I will try to argue this is a useful action and that keeping it in Bylaws
> does not change regular release process.
>
> - Bylaws do not require to vote on every release plan.
> If nobody complains then it is a routine process of building a RC and
> voting on it.
> - It is useful to vote on a release plan when there are concerns about how
> that particular plan effects the evolution of the project.
> It is better to reach consensus on intentions rather than disagree when
> the release is ready.
>
> This is also a way to unite the community to work in common direction and
> avoid fragmentation of the project.
> Otherwise people who do not support the direction keep developing their
> own branches and forks.
>
> I like the second change defining the role of RM.
> Very well formulated, thanks Matt.
>
> --Konstantin
>
>
> On Tue, May 21, 2013 at 7:01 PM, Matt Foley <ma...@apache.org> wrote:
>
>> Ok, if no one complains I will phrase the vote to include +1's explicitly
>> cast in the discussion thread.
>> --Matt
>>
>>
>> On Tue, May 21, 2013 at 6:58 PM, Mattmann, Chris A (398J) <
>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>
>> > Why repeat just tally new ones?
>> >
>> > Sent from my iPhone
>> >
>> > On May 21, 2013, at 6:58 PM, "Matt Foley" <ma...@apache.org> wrote:
>> >
>> > > 13/14 +1's. I think that constitutes consensus. Moving this to a
>> VOTE
>> > > thread. Please repeat your +1s :-)
>> > > Cheers,
>> > > --Matt
>> > >
>> > >
>> > > On Tue, May 21, 2013 at 5:33 PM, Mahadev Konar <
>> mahadev@hortonworks.com
>> > >wrote:
>> > >
>> > >> +1.
>> > >>
>> > >> thanks
>> > >> mahadev
>> > >>
>> > >> On Tue, May 21, 2013 at 4:48 PM, Karthik Kambatla <
>> kasha@cloudera.com>
>> > >> wrote:
>> > >>> +1 (non-binding)
>> > >>>
>> > >>>
>> > >>> On Tue, May 21, 2013 at 4:13 PM, Jitendra Pandey
>> > >>> <ji...@hortonworks.com>wrote:
>> > >>>
>> > >>>> +1
>> > >>>>
>> > >>>>
>> > >>>> On Tue, May 21, 2013 at 4:02 PM, Eli Collins <el...@cloudera.com>
>> > wrote:
>> > >>>>
>> > >>>>> +1 thanks Matt.
>> > >>>>>
>> > >>>>>
>> > >>>>> On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org>
>> > wrote:
>> > >>>>>
>> > >>>>>> Hi all,
>> > >>>>>> This has been a side topic in several email threads recently.
>> > >>>> Currently
>> > >>>>> we
>> > >>>>>> have an ambiguity. We have a tradition in the dev community that
>> > >> any
>> > >>>>>> committer can create a branch, and propose release candidates
>> from
>> > >> it.
>> > >>>>> Yet
>> > >>>>>> the Hadoop bylaws say that releases have to be planned in
>> advance,
>> > >> the
>> > >>>>> plan
>> > >>>>>> needs to be voted on, and presumably can be denied.
>> > >>>>>>
>> > >>>>>> Apache policies (primarily here <
>> > >>>> http://www.apache.org/dev/release.html>
>> > >>>>>> and here <http://www.apache.org/foundation/voting.html>, with
>> > >>>>>> non-normative commentary
>> > >>>>>> here<
>> > >>>>
>> > http://incubator.apache.org/guides/releasemanagement.html#best-practice
>> > >>>>>> )
>> > >>>>>> are very clear on how Releases have to be approved, and our
>> bylaws
>> > >> are
>> > >>>>>> consistent with those policies. But Apache policies don't say
>> > >> anything
>> > >>>>>> I've found about Release Plans, nor about voting on Release
>> Plans.
>> > >>>>>>
>> > >>>>>> I propose the following change, to remove Release Plan votes, and
>> > >> give
>> > >>>> a
>> > >>>>>> simple definition of Release Manager role. I'm opening
>> discussion
>> > >> with
>> > >>>>>> this proposal, and will put it to a vote if we seem to be getting
>> > >>>>>> consensus. Here's the changes I suggest in the
>> > >>>>>> Bylaws<http://hadoop.apache.org/bylaws.html>
>> > >>>>>> document:
>> > >>>>>>
>> > >>>>>> ===
>> > >>>>>>
>> > >>>>>> 1. In the "Decision Making" : "Actions" section of the Bylaws,
>> the
>> > >>>>>> following text is removed:
>> > >>>>>>
>> > >>>>>> ** Release Plan*
>> > >>>>>>
>> > >>>>>> Defines the timetable and actions for a release. The plan also
>> > >>>> nominates
>> > >>>>> a
>> > >>>>>> Release Manager.
>> > >>>>>>
>> > >>>>>> Lazy majority of active committers
>> > >>>>>>
>> > >>>>>>
>> > >>>>>> 2. In the "Roles and Responsibilities" section of the Bylaws, an
>> > >>>>> additional
>> > >>>>>> role is defined:
>> > >>>>>>
>> > >>>>>> ** Release Manager*
>> > >>>>>>
>> > >>>>>> A Release Manager (RM) is a committer who volunteers to produce a
>> > >>>> Release
>> > >>>>>> Candidate according to
>> > >>>>>> HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
>> > >>>>>> The RM shall publish a Release Plan on the *common-dev@* list
>> > >> stating
>> > >>>>> the
>> > >>>>>> branch from which they intend to make a Release Candidate, at
>> least
>> > >> one
>> > >>>>>> week before they do so. The RM is responsible for building
>> consensus
>> > >>>>> around
>> > >>>>>> the content of the Release Candidate, in order to achieve a
>> > >> successful
>> > >>>>>> Product Release vote.
>> > >>>>>>
>> > >>>>>> ===
>> > >>>>>>
>> > >>>>>> Please share your views.
>> > >>>>>> Best regards,
>> > >>>>>> --Matt (long-time release manager)
>> > >>>>
>> > >>>>
>> > >>>>
>> > >>>> --
>> > >>>> <http://hortonworks.com/download/>
>> > >>
>> >
>>
>
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Konstantin Shvachko <sh...@gmail.com>.
Couldn't reply yesterday.
I will try to argue this is a useful action and that keeping it in Bylaws
does not change regular release process.
- Bylaws do not require to vote on every release plan.
If nobody complains then it is a routine process of building a RC and
voting on it.
- It is useful to vote on a release plan when there are concerns about how
that particular plan effects the evolution of the project.
It is better to reach consensus on intentions rather than disagree when the
release is ready.
This is also a way to unite the community to work in common direction and
avoid fragmentation of the project.
Otherwise people who do not support the direction keep developing their own
branches and forks.
I like the second change defining the role of RM.
Very well formulated, thanks Matt.
--Konstantin
On Tue, May 21, 2013 at 7:01 PM, Matt Foley <ma...@apache.org> wrote:
> Ok, if no one complains I will phrase the vote to include +1's explicitly
> cast in the discussion thread.
> --Matt
>
>
> On Tue, May 21, 2013 at 6:58 PM, Mattmann, Chris A (398J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
> > Why repeat just tally new ones?
> >
> > Sent from my iPhone
> >
> > On May 21, 2013, at 6:58 PM, "Matt Foley" <ma...@apache.org> wrote:
> >
> > > 13/14 +1's. I think that constitutes consensus. Moving this to a VOTE
> > > thread. Please repeat your +1s :-)
> > > Cheers,
> > > --Matt
> > >
> > >
> > > On Tue, May 21, 2013 at 5:33 PM, Mahadev Konar <
> mahadev@hortonworks.com
> > >wrote:
> > >
> > >> +1.
> > >>
> > >> thanks
> > >> mahadev
> > >>
> > >> On Tue, May 21, 2013 at 4:48 PM, Karthik Kambatla <kasha@cloudera.com
> >
> > >> wrote:
> > >>> +1 (non-binding)
> > >>>
> > >>>
> > >>> On Tue, May 21, 2013 at 4:13 PM, Jitendra Pandey
> > >>> <ji...@hortonworks.com>wrote:
> > >>>
> > >>>> +1
> > >>>>
> > >>>>
> > >>>> On Tue, May 21, 2013 at 4:02 PM, Eli Collins <el...@cloudera.com>
> > wrote:
> > >>>>
> > >>>>> +1 thanks Matt.
> > >>>>>
> > >>>>>
> > >>>>> On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org>
> > wrote:
> > >>>>>
> > >>>>>> Hi all,
> > >>>>>> This has been a side topic in several email threads recently.
> > >>>> Currently
> > >>>>> we
> > >>>>>> have an ambiguity. We have a tradition in the dev community that
> > >> any
> > >>>>>> committer can create a branch, and propose release candidates from
> > >> it.
> > >>>>> Yet
> > >>>>>> the Hadoop bylaws say that releases have to be planned in advance,
> > >> the
> > >>>>> plan
> > >>>>>> needs to be voted on, and presumably can be denied.
> > >>>>>>
> > >>>>>> Apache policies (primarily here <
> > >>>> http://www.apache.org/dev/release.html>
> > >>>>>> and here <http://www.apache.org/foundation/voting.html>, with
> > >>>>>> non-normative commentary
> > >>>>>> here<
> > >>>>
> > http://incubator.apache.org/guides/releasemanagement.html#best-practice
> > >>>>>> )
> > >>>>>> are very clear on how Releases have to be approved, and our bylaws
> > >> are
> > >>>>>> consistent with those policies. But Apache policies don't say
> > >> anything
> > >>>>>> I've found about Release Plans, nor about voting on Release Plans.
> > >>>>>>
> > >>>>>> I propose the following change, to remove Release Plan votes, and
> > >> give
> > >>>> a
> > >>>>>> simple definition of Release Manager role. I'm opening discussion
> > >> with
> > >>>>>> this proposal, and will put it to a vote if we seem to be getting
> > >>>>>> consensus. Here's the changes I suggest in the
> > >>>>>> Bylaws<http://hadoop.apache.org/bylaws.html>
> > >>>>>> document:
> > >>>>>>
> > >>>>>> ===
> > >>>>>>
> > >>>>>> 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> > >>>>>> following text is removed:
> > >>>>>>
> > >>>>>> ** Release Plan*
> > >>>>>>
> > >>>>>> Defines the timetable and actions for a release. The plan also
> > >>>> nominates
> > >>>>> a
> > >>>>>> Release Manager.
> > >>>>>>
> > >>>>>> Lazy majority of active committers
> > >>>>>>
> > >>>>>>
> > >>>>>> 2. In the "Roles and Responsibilities" section of the Bylaws, an
> > >>>>> additional
> > >>>>>> role is defined:
> > >>>>>>
> > >>>>>> ** Release Manager*
> > >>>>>>
> > >>>>>> A Release Manager (RM) is a committer who volunteers to produce a
> > >>>> Release
> > >>>>>> Candidate according to
> > >>>>>> HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> > >>>>>> The RM shall publish a Release Plan on the *common-dev@* list
> > >> stating
> > >>>>> the
> > >>>>>> branch from which they intend to make a Release Candidate, at
> least
> > >> one
> > >>>>>> week before they do so. The RM is responsible for building
> consensus
> > >>>>> around
> > >>>>>> the content of the Release Candidate, in order to achieve a
> > >> successful
> > >>>>>> Product Release vote.
> > >>>>>>
> > >>>>>> ===
> > >>>>>>
> > >>>>>> Please share your views.
> > >>>>>> Best regards,
> > >>>>>> --Matt (long-time release manager)
> > >>>>
> > >>>>
> > >>>>
> > >>>> --
> > >>>> <http://hortonworks.com/download/>
> > >>
> >
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Matt Foley <ma...@apache.org>.
Ok, if no one complains I will phrase the vote to include +1's explicitly
cast in the discussion thread.
--Matt
On Tue, May 21, 2013 at 6:58 PM, Mattmann, Chris A (398J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> Why repeat just tally new ones?
>
> Sent from my iPhone
>
> On May 21, 2013, at 6:58 PM, "Matt Foley" <ma...@apache.org> wrote:
>
> > 13/14 +1's. I think that constitutes consensus. Moving this to a VOTE
> > thread. Please repeat your +1s :-)
> > Cheers,
> > --Matt
> >
> >
> > On Tue, May 21, 2013 at 5:33 PM, Mahadev Konar <mahadev@hortonworks.com
> >wrote:
> >
> >> +1.
> >>
> >> thanks
> >> mahadev
> >>
> >> On Tue, May 21, 2013 at 4:48 PM, Karthik Kambatla <ka...@cloudera.com>
> >> wrote:
> >>> +1 (non-binding)
> >>>
> >>>
> >>> On Tue, May 21, 2013 at 4:13 PM, Jitendra Pandey
> >>> <ji...@hortonworks.com>wrote:
> >>>
> >>>> +1
> >>>>
> >>>>
> >>>> On Tue, May 21, 2013 at 4:02 PM, Eli Collins <el...@cloudera.com>
> wrote:
> >>>>
> >>>>> +1 thanks Matt.
> >>>>>
> >>>>>
> >>>>> On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org>
> wrote:
> >>>>>
> >>>>>> Hi all,
> >>>>>> This has been a side topic in several email threads recently.
> >>>> Currently
> >>>>> we
> >>>>>> have an ambiguity. We have a tradition in the dev community that
> >> any
> >>>>>> committer can create a branch, and propose release candidates from
> >> it.
> >>>>> Yet
> >>>>>> the Hadoop bylaws say that releases have to be planned in advance,
> >> the
> >>>>> plan
> >>>>>> needs to be voted on, and presumably can be denied.
> >>>>>>
> >>>>>> Apache policies (primarily here <
> >>>> http://www.apache.org/dev/release.html>
> >>>>>> and here <http://www.apache.org/foundation/voting.html>, with
> >>>>>> non-normative commentary
> >>>>>> here<
> >>>>
> http://incubator.apache.org/guides/releasemanagement.html#best-practice
> >>>>>> )
> >>>>>> are very clear on how Releases have to be approved, and our bylaws
> >> are
> >>>>>> consistent with those policies. But Apache policies don't say
> >> anything
> >>>>>> I've found about Release Plans, nor about voting on Release Plans.
> >>>>>>
> >>>>>> I propose the following change, to remove Release Plan votes, and
> >> give
> >>>> a
> >>>>>> simple definition of Release Manager role. I'm opening discussion
> >> with
> >>>>>> this proposal, and will put it to a vote if we seem to be getting
> >>>>>> consensus. Here's the changes I suggest in the
> >>>>>> Bylaws<http://hadoop.apache.org/bylaws.html>
> >>>>>> document:
> >>>>>>
> >>>>>> ===
> >>>>>>
> >>>>>> 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> >>>>>> following text is removed:
> >>>>>>
> >>>>>> ** Release Plan*
> >>>>>>
> >>>>>> Defines the timetable and actions for a release. The plan also
> >>>> nominates
> >>>>> a
> >>>>>> Release Manager.
> >>>>>>
> >>>>>> Lazy majority of active committers
> >>>>>>
> >>>>>>
> >>>>>> 2. In the "Roles and Responsibilities" section of the Bylaws, an
> >>>>> additional
> >>>>>> role is defined:
> >>>>>>
> >>>>>> ** Release Manager*
> >>>>>>
> >>>>>> A Release Manager (RM) is a committer who volunteers to produce a
> >>>> Release
> >>>>>> Candidate according to
> >>>>>> HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> >>>>>> The RM shall publish a Release Plan on the *common-dev@* list
> >> stating
> >>>>> the
> >>>>>> branch from which they intend to make a Release Candidate, at least
> >> one
> >>>>>> week before they do so. The RM is responsible for building consensus
> >>>>> around
> >>>>>> the content of the Release Candidate, in order to achieve a
> >> successful
> >>>>>> Product Release vote.
> >>>>>>
> >>>>>> ===
> >>>>>>
> >>>>>> Please share your views.
> >>>>>> Best regards,
> >>>>>> --Matt (long-time release manager)
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> <http://hortonworks.com/download/>
> >>
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.
Why repeat just tally new ones?
Sent from my iPhone
On May 21, 2013, at 6:58 PM, "Matt Foley" <ma...@apache.org> wrote:
> 13/14 +1's. I think that constitutes consensus. Moving this to a VOTE
> thread. Please repeat your +1s :-)
> Cheers,
> --Matt
>
>
> On Tue, May 21, 2013 at 5:33 PM, Mahadev Konar <ma...@hortonworks.com>wrote:
>
>> +1.
>>
>> thanks
>> mahadev
>>
>> On Tue, May 21, 2013 at 4:48 PM, Karthik Kambatla <ka...@cloudera.com>
>> wrote:
>>> +1 (non-binding)
>>>
>>>
>>> On Tue, May 21, 2013 at 4:13 PM, Jitendra Pandey
>>> <ji...@hortonworks.com>wrote:
>>>
>>>> +1
>>>>
>>>>
>>>> On Tue, May 21, 2013 at 4:02 PM, Eli Collins <el...@cloudera.com> wrote:
>>>>
>>>>> +1 thanks Matt.
>>>>>
>>>>>
>>>>> On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
>>>>>
>>>>>> Hi all,
>>>>>> This has been a side topic in several email threads recently.
>>>> Currently
>>>>> we
>>>>>> have an ambiguity. We have a tradition in the dev community that
>> any
>>>>>> committer can create a branch, and propose release candidates from
>> it.
>>>>> Yet
>>>>>> the Hadoop bylaws say that releases have to be planned in advance,
>> the
>>>>> plan
>>>>>> needs to be voted on, and presumably can be denied.
>>>>>>
>>>>>> Apache policies (primarily here <
>>>> http://www.apache.org/dev/release.html>
>>>>>> and here <http://www.apache.org/foundation/voting.html>, with
>>>>>> non-normative commentary
>>>>>> here<
>>>> http://incubator.apache.org/guides/releasemanagement.html#best-practice
>>>>>> )
>>>>>> are very clear on how Releases have to be approved, and our bylaws
>> are
>>>>>> consistent with those policies. But Apache policies don't say
>> anything
>>>>>> I've found about Release Plans, nor about voting on Release Plans.
>>>>>>
>>>>>> I propose the following change, to remove Release Plan votes, and
>> give
>>>> a
>>>>>> simple definition of Release Manager role. I'm opening discussion
>> with
>>>>>> this proposal, and will put it to a vote if we seem to be getting
>>>>>> consensus. Here's the changes I suggest in the
>>>>>> Bylaws<http://hadoop.apache.org/bylaws.html>
>>>>>> document:
>>>>>>
>>>>>> ===
>>>>>>
>>>>>> 1. In the "Decision Making" : "Actions" section of the Bylaws, the
>>>>>> following text is removed:
>>>>>>
>>>>>> ** Release Plan*
>>>>>>
>>>>>> Defines the timetable and actions for a release. The plan also
>>>> nominates
>>>>> a
>>>>>> Release Manager.
>>>>>>
>>>>>> Lazy majority of active committers
>>>>>>
>>>>>>
>>>>>> 2. In the "Roles and Responsibilities" section of the Bylaws, an
>>>>> additional
>>>>>> role is defined:
>>>>>>
>>>>>> ** Release Manager*
>>>>>>
>>>>>> A Release Manager (RM) is a committer who volunteers to produce a
>>>> Release
>>>>>> Candidate according to
>>>>>> HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
>>>>>> The RM shall publish a Release Plan on the *common-dev@* list
>> stating
>>>>> the
>>>>>> branch from which they intend to make a Release Candidate, at least
>> one
>>>>>> week before they do so. The RM is responsible for building consensus
>>>>> around
>>>>>> the content of the Release Candidate, in order to achieve a
>> successful
>>>>>> Product Release vote.
>>>>>>
>>>>>> ===
>>>>>>
>>>>>> Please share your views.
>>>>>> Best regards,
>>>>>> --Matt (long-time release manager)
>>>>
>>>>
>>>>
>>>> --
>>>> <http://hortonworks.com/download/>
>>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Matt Foley <ma...@apache.org>.
13/14 +1's. I think that constitutes consensus. Moving this to a VOTE
thread. Please repeat your +1s :-)
Cheers,
--Matt
On Tue, May 21, 2013 at 5:33 PM, Mahadev Konar <ma...@hortonworks.com>wrote:
> +1.
>
> thanks
> mahadev
>
> On Tue, May 21, 2013 at 4:48 PM, Karthik Kambatla <ka...@cloudera.com>
> wrote:
> > +1 (non-binding)
> >
> >
> > On Tue, May 21, 2013 at 4:13 PM, Jitendra Pandey
> > <ji...@hortonworks.com>wrote:
> >
> >> +1
> >>
> >>
> >> On Tue, May 21, 2013 at 4:02 PM, Eli Collins <el...@cloudera.com> wrote:
> >>
> >> > +1 thanks Matt.
> >> >
> >> >
> >> > On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
> >> >
> >> > > Hi all,
> >> > > This has been a side topic in several email threads recently.
> >> Currently
> >> > we
> >> > > have an ambiguity. We have a tradition in the dev community that
> any
> >> > > committer can create a branch, and propose release candidates from
> it.
> >> > Yet
> >> > > the Hadoop bylaws say that releases have to be planned in advance,
> the
> >> > plan
> >> > > needs to be voted on, and presumably can be denied.
> >> > >
> >> > > Apache policies (primarily here <
> >> http://www.apache.org/dev/release.html>
> >> > > and here <http://www.apache.org/foundation/voting.html>, with
> >> > > non-normative commentary
> >> > > here<
> >> > >
> >> http://incubator.apache.org/guides/releasemanagement.html#best-practice
> >> > >)
> >> > > are very clear on how Releases have to be approved, and our bylaws
> are
> >> > > consistent with those policies. But Apache policies don't say
> anything
> >> > > I've found about Release Plans, nor about voting on Release Plans.
> >> > >
> >> > > I propose the following change, to remove Release Plan votes, and
> give
> >> a
> >> > > simple definition of Release Manager role. I'm opening discussion
> with
> >> > > this proposal, and will put it to a vote if we seem to be getting
> >> > > consensus. Here's the changes I suggest in the
> >> > > Bylaws<http://hadoop.apache.org/bylaws.html>
> >> > > document:
> >> > >
> >> > > ===
> >> > >
> >> > > 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> >> > > following text is removed:
> >> > >
> >> > > ** Release Plan*
> >> > >
> >> > > Defines the timetable and actions for a release. The plan also
> >> nominates
> >> > a
> >> > > Release Manager.
> >> > >
> >> > > Lazy majority of active committers
> >> > >
> >> > >
> >> > > 2. In the "Roles and Responsibilities" section of the Bylaws, an
> >> > additional
> >> > > role is defined:
> >> > >
> >> > > ** Release Manager*
> >> > >
> >> > > A Release Manager (RM) is a committer who volunteers to produce a
> >> Release
> >> > > Candidate according to
> >> > > HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> >> > > The RM shall publish a Release Plan on the *common-dev@* list
> stating
> >> > the
> >> > > branch from which they intend to make a Release Candidate, at least
> one
> >> > > week before they do so. The RM is responsible for building consensus
> >> > around
> >> > > the content of the Release Candidate, in order to achieve a
> successful
> >> > > Product Release vote.
> >> > >
> >> > > ===
> >> > >
> >> > > Please share your views.
> >> > > Best regards,
> >> > > --Matt (long-time release manager)
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> <http://hortonworks.com/download/>
> >>
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Mahadev Konar <ma...@hortonworks.com>.
+1.
thanks
mahadev
On Tue, May 21, 2013 at 4:48 PM, Karthik Kambatla <ka...@cloudera.com> wrote:
> +1 (non-binding)
>
>
> On Tue, May 21, 2013 at 4:13 PM, Jitendra Pandey
> <ji...@hortonworks.com>wrote:
>
>> +1
>>
>>
>> On Tue, May 21, 2013 at 4:02 PM, Eli Collins <el...@cloudera.com> wrote:
>>
>> > +1 thanks Matt.
>> >
>> >
>> > On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
>> >
>> > > Hi all,
>> > > This has been a side topic in several email threads recently.
>> Currently
>> > we
>> > > have an ambiguity. We have a tradition in the dev community that any
>> > > committer can create a branch, and propose release candidates from it.
>> > Yet
>> > > the Hadoop bylaws say that releases have to be planned in advance, the
>> > plan
>> > > needs to be voted on, and presumably can be denied.
>> > >
>> > > Apache policies (primarily here <
>> http://www.apache.org/dev/release.html>
>> > > and here <http://www.apache.org/foundation/voting.html>, with
>> > > non-normative commentary
>> > > here<
>> > >
>> http://incubator.apache.org/guides/releasemanagement.html#best-practice
>> > >)
>> > > are very clear on how Releases have to be approved, and our bylaws are
>> > > consistent with those policies. But Apache policies don't say anything
>> > > I've found about Release Plans, nor about voting on Release Plans.
>> > >
>> > > I propose the following change, to remove Release Plan votes, and give
>> a
>> > > simple definition of Release Manager role. I'm opening discussion with
>> > > this proposal, and will put it to a vote if we seem to be getting
>> > > consensus. Here's the changes I suggest in the
>> > > Bylaws<http://hadoop.apache.org/bylaws.html>
>> > > document:
>> > >
>> > > ===
>> > >
>> > > 1. In the "Decision Making" : "Actions" section of the Bylaws, the
>> > > following text is removed:
>> > >
>> > > ** Release Plan*
>> > >
>> > > Defines the timetable and actions for a release. The plan also
>> nominates
>> > a
>> > > Release Manager.
>> > >
>> > > Lazy majority of active committers
>> > >
>> > >
>> > > 2. In the "Roles and Responsibilities" section of the Bylaws, an
>> > additional
>> > > role is defined:
>> > >
>> > > ** Release Manager*
>> > >
>> > > A Release Manager (RM) is a committer who volunteers to produce a
>> Release
>> > > Candidate according to
>> > > HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
>> > > The RM shall publish a Release Plan on the *common-dev@* list stating
>> > the
>> > > branch from which they intend to make a Release Candidate, at least one
>> > > week before they do so. The RM is responsible for building consensus
>> > around
>> > > the content of the Release Candidate, in order to achieve a successful
>> > > Product Release vote.
>> > >
>> > > ===
>> > >
>> > > Please share your views.
>> > > Best regards,
>> > > --Matt (long-time release manager)
>> > >
>> >
>>
>>
>>
>> --
>> <http://hortonworks.com/download/>
>>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Karthik Kambatla <ka...@cloudera.com>.
+1 (non-binding)
On Tue, May 21, 2013 at 4:13 PM, Jitendra Pandey
<ji...@hortonworks.com>wrote:
> +1
>
>
> On Tue, May 21, 2013 at 4:02 PM, Eli Collins <el...@cloudera.com> wrote:
>
> > +1 thanks Matt.
> >
> >
> > On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
> >
> > > Hi all,
> > > This has been a side topic in several email threads recently.
> Currently
> > we
> > > have an ambiguity. We have a tradition in the dev community that any
> > > committer can create a branch, and propose release candidates from it.
> > Yet
> > > the Hadoop bylaws say that releases have to be planned in advance, the
> > plan
> > > needs to be voted on, and presumably can be denied.
> > >
> > > Apache policies (primarily here <
> http://www.apache.org/dev/release.html>
> > > and here <http://www.apache.org/foundation/voting.html>, with
> > > non-normative commentary
> > > here<
> > >
> http://incubator.apache.org/guides/releasemanagement.html#best-practice
> > >)
> > > are very clear on how Releases have to be approved, and our bylaws are
> > > consistent with those policies. But Apache policies don't say anything
> > > I've found about Release Plans, nor about voting on Release Plans.
> > >
> > > I propose the following change, to remove Release Plan votes, and give
> a
> > > simple definition of Release Manager role. I'm opening discussion with
> > > this proposal, and will put it to a vote if we seem to be getting
> > > consensus. Here's the changes I suggest in the
> > > Bylaws<http://hadoop.apache.org/bylaws.html>
> > > document:
> > >
> > > ===
> > >
> > > 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> > > following text is removed:
> > >
> > > ** Release Plan*
> > >
> > > Defines the timetable and actions for a release. The plan also
> nominates
> > a
> > > Release Manager.
> > >
> > > Lazy majority of active committers
> > >
> > >
> > > 2. In the "Roles and Responsibilities" section of the Bylaws, an
> > additional
> > > role is defined:
> > >
> > > ** Release Manager*
> > >
> > > A Release Manager (RM) is a committer who volunteers to produce a
> Release
> > > Candidate according to
> > > HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> > > The RM shall publish a Release Plan on the *common-dev@* list stating
> > the
> > > branch from which they intend to make a Release Candidate, at least one
> > > week before they do so. The RM is responsible for building consensus
> > around
> > > the content of the Release Candidate, in order to achieve a successful
> > > Product Release vote.
> > >
> > > ===
> > >
> > > Please share your views.
> > > Best regards,
> > > --Matt (long-time release manager)
> > >
> >
>
>
>
> --
> <http://hortonworks.com/download/>
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Jitendra Pandey <ji...@hortonworks.com>.
+1
On Tue, May 21, 2013 at 4:02 PM, Eli Collins <el...@cloudera.com> wrote:
> +1 thanks Matt.
>
>
> On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
>
> > Hi all,
> > This has been a side topic in several email threads recently. Currently
> we
> > have an ambiguity. We have a tradition in the dev community that any
> > committer can create a branch, and propose release candidates from it.
> Yet
> > the Hadoop bylaws say that releases have to be planned in advance, the
> plan
> > needs to be voted on, and presumably can be denied.
> >
> > Apache policies (primarily here <http://www.apache.org/dev/release.html>
> > and here <http://www.apache.org/foundation/voting.html>, with
> > non-normative commentary
> > here<
> > http://incubator.apache.org/guides/releasemanagement.html#best-practice
> >)
> > are very clear on how Releases have to be approved, and our bylaws are
> > consistent with those policies. But Apache policies don't say anything
> > I've found about Release Plans, nor about voting on Release Plans.
> >
> > I propose the following change, to remove Release Plan votes, and give a
> > simple definition of Release Manager role. I'm opening discussion with
> > this proposal, and will put it to a vote if we seem to be getting
> > consensus. Here's the changes I suggest in the
> > Bylaws<http://hadoop.apache.org/bylaws.html>
> > document:
> >
> > ===
> >
> > 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> > following text is removed:
> >
> > ** Release Plan*
> >
> > Defines the timetable and actions for a release. The plan also nominates
> a
> > Release Manager.
> >
> > Lazy majority of active committers
> >
> >
> > 2. In the "Roles and Responsibilities" section of the Bylaws, an
> additional
> > role is defined:
> >
> > ** Release Manager*
> >
> > A Release Manager (RM) is a committer who volunteers to produce a Release
> > Candidate according to
> > HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> > The RM shall publish a Release Plan on the *common-dev@* list stating
> the
> > branch from which they intend to make a Release Candidate, at least one
> > week before they do so. The RM is responsible for building consensus
> around
> > the content of the Release Candidate, in order to achieve a successful
> > Product Release vote.
> >
> > ===
> >
> > Please share your views.
> > Best regards,
> > --Matt (long-time release manager)
> >
>
--
<http://hortonworks.com/download/>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Sandy Ryza <sa...@cloudera.com>.
+1 (non-binding)
On Tue, May 21, 2013 at 4:02 PM, Eli Collins <el...@cloudera.com> wrote:
> +1 thanks Matt.
>
>
> On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
>
> > Hi all,
> > This has been a side topic in several email threads recently. Currently
> we
> > have an ambiguity. We have a tradition in the dev community that any
> > committer can create a branch, and propose release candidates from it.
> Yet
> > the Hadoop bylaws say that releases have to be planned in advance, the
> plan
> > needs to be voted on, and presumably can be denied.
> >
> > Apache policies (primarily here <http://www.apache.org/dev/release.html>
> > and here <http://www.apache.org/foundation/voting.html>, with
> > non-normative commentary
> > here<
> > http://incubator.apache.org/guides/releasemanagement.html#best-practice
> >)
> > are very clear on how Releases have to be approved, and our bylaws are
> > consistent with those policies. But Apache policies don't say anything
> > I've found about Release Plans, nor about voting on Release Plans.
> >
> > I propose the following change, to remove Release Plan votes, and give a
> > simple definition of Release Manager role. I'm opening discussion with
> > this proposal, and will put it to a vote if we seem to be getting
> > consensus. Here's the changes I suggest in the
> > Bylaws<http://hadoop.apache.org/bylaws.html>
> > document:
> >
> > ===
> >
> > 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> > following text is removed:
> >
> > ** Release Plan*
> >
> > Defines the timetable and actions for a release. The plan also nominates
> a
> > Release Manager.
> >
> > Lazy majority of active committers
> >
> >
> > 2. In the "Roles and Responsibilities" section of the Bylaws, an
> additional
> > role is defined:
> >
> > ** Release Manager*
> >
> > A Release Manager (RM) is a committer who volunteers to produce a Release
> > Candidate according to
> > HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> > The RM shall publish a Release Plan on the *common-dev@* list stating
> the
> > branch from which they intend to make a Release Candidate, at least one
> > week before they do so. The RM is responsible for building consensus
> around
> > the content of the Release Candidate, in order to achieve a successful
> > Product Release vote.
> >
> > ===
> >
> > Please share your views.
> > Best regards,
> > --Matt (long-time release manager)
> >
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Eli Collins <el...@cloudera.com>.
+1 thanks Matt.
On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
> Hi all,
> This has been a side topic in several email threads recently. Currently we
> have an ambiguity. We have a tradition in the dev community that any
> committer can create a branch, and propose release candidates from it. Yet
> the Hadoop bylaws say that releases have to be planned in advance, the plan
> needs to be voted on, and presumably can be denied.
>
> Apache policies (primarily here <http://www.apache.org/dev/release.html>
> and here <http://www.apache.org/foundation/voting.html>, with
> non-normative commentary
> here<
> http://incubator.apache.org/guides/releasemanagement.html#best-practice>)
> are very clear on how Releases have to be approved, and our bylaws are
> consistent with those policies. But Apache policies don't say anything
> I've found about Release Plans, nor about voting on Release Plans.
>
> I propose the following change, to remove Release Plan votes, and give a
> simple definition of Release Manager role. I'm opening discussion with
> this proposal, and will put it to a vote if we seem to be getting
> consensus. Here's the changes I suggest in the
> Bylaws<http://hadoop.apache.org/bylaws.html>
> document:
>
> ===
>
> 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> following text is removed:
>
> ** Release Plan*
>
> Defines the timetable and actions for a release. The plan also nominates a
> Release Manager.
>
> Lazy majority of active committers
>
>
> 2. In the "Roles and Responsibilities" section of the Bylaws, an additional
> role is defined:
>
> ** Release Manager*
>
> A Release Manager (RM) is a committer who volunteers to produce a Release
> Candidate according to
> HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> The RM shall publish a Release Plan on the *common-dev@* list stating the
> branch from which they intend to make a Release Candidate, at least one
> week before they do so. The RM is responsible for building consensus around
> the content of the Release Candidate, in order to achieve a successful
> Product Release vote.
>
> ===
>
> Please share your views.
> Best regards,
> --Matt (long-time release manager)
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Arpit Agarwal <aa...@hortonworks.com>.
+1 (non-binding)
On Wed, May 22, 2013 at 10:04 AM, Roman Shaposhnik <rv...@apache.org> wrote:
> +1 (non-binding)
>
> On Wed, May 22, 2013 at 10:00 AM, Chris Nauroth
> <cn...@hortonworks.com> wrote:
> > +1 (non-binding)
> >
> > Chris Nauroth
> > Hortonworks
> > http://hortonworks.com/
> >
> >
> >
> > On Wed, May 22, 2013 at 7:58 AM, Tom White <to...@cloudera.com> wrote:
> >
> >> +1
> >>
> >> Cheers,
> >> Tom
> >>
> >> On Tue, May 21, 2013 at 10:10 PM, Matt Foley <ma...@apache.org> wrote:
> >> > Hi all,
> >> > This has been a side topic in several email threads recently.
> Currently
> >> we
> >> > have an ambiguity. We have a tradition in the dev community that any
> >> > committer can create a branch, and propose release candidates from it.
> >> Yet
> >> > the Hadoop bylaws say that releases have to be planned in advance, the
> >> plan
> >> > needs to be voted on, and presumably can be denied.
> >> >
> >> > Apache policies (primarily here <
> http://www.apache.org/dev/release.html>
> >> > and here <http://www.apache.org/foundation/voting.html>, with
> >> > non-normative commentary
> >> > here<
> >> http://incubator.apache.org/guides/releasemanagement.html#best-practice
> >)
> >> > are very clear on how Releases have to be approved, and our bylaws are
> >> > consistent with those policies. But Apache policies don't say
> anything
> >> > I've found about Release Plans, nor about voting on Release Plans.
> >> >
> >> > I propose the following change, to remove Release Plan votes, and
> give a
> >> > simple definition of Release Manager role. I'm opening discussion
> with
> >> > this proposal, and will put it to a vote if we seem to be getting
> >> > consensus. Here's the changes I suggest in the
> >> > Bylaws<http://hadoop.apache.org/bylaws.html>
> >> > document:
> >> >
> >> > ===
> >> >
> >> > 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> >> > following text is removed:
> >> >
> >> > ** Release Plan*
> >> >
> >> > Defines the timetable and actions for a release. The plan also
> nominates
> >> a
> >> > Release Manager.
> >> >
> >> > Lazy majority of active committers
> >> >
> >> >
> >> > 2. In the "Roles and Responsibilities" section of the Bylaws, an
> >> additional
> >> > role is defined:
> >> >
> >> > ** Release Manager*
> >> >
> >> > A Release Manager (RM) is a committer who volunteers to produce a
> Release
> >> > Candidate according to
> >> > HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> >> > The RM shall publish a Release Plan on the *common-dev@* list
> stating
> >> the
> >> > branch from which they intend to make a Release Candidate, at least
> one
> >> > week before they do so. The RM is responsible for building consensus
> >> around
> >> > the content of the Release Candidate, in order to achieve a successful
> >> > Product Release vote.
> >> >
> >> > ===
> >> >
> >> > Please share your views.
> >> > Best regards,
> >> > --Matt (long-time release manager)
> >>
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Roman Shaposhnik <rv...@apache.org>.
+1 (non-binding)
On Wed, May 22, 2013 at 10:00 AM, Chris Nauroth
<cn...@hortonworks.com> wrote:
> +1 (non-binding)
>
> Chris Nauroth
> Hortonworks
> http://hortonworks.com/
>
>
>
> On Wed, May 22, 2013 at 7:58 AM, Tom White <to...@cloudera.com> wrote:
>
>> +1
>>
>> Cheers,
>> Tom
>>
>> On Tue, May 21, 2013 at 10:10 PM, Matt Foley <ma...@apache.org> wrote:
>> > Hi all,
>> > This has been a side topic in several email threads recently. Currently
>> we
>> > have an ambiguity. We have a tradition in the dev community that any
>> > committer can create a branch, and propose release candidates from it.
>> Yet
>> > the Hadoop bylaws say that releases have to be planned in advance, the
>> plan
>> > needs to be voted on, and presumably can be denied.
>> >
>> > Apache policies (primarily here <http://www.apache.org/dev/release.html>
>> > and here <http://www.apache.org/foundation/voting.html>, with
>> > non-normative commentary
>> > here<
>> http://incubator.apache.org/guides/releasemanagement.html#best-practice>)
>> > are very clear on how Releases have to be approved, and our bylaws are
>> > consistent with those policies. But Apache policies don't say anything
>> > I've found about Release Plans, nor about voting on Release Plans.
>> >
>> > I propose the following change, to remove Release Plan votes, and give a
>> > simple definition of Release Manager role. I'm opening discussion with
>> > this proposal, and will put it to a vote if we seem to be getting
>> > consensus. Here's the changes I suggest in the
>> > Bylaws<http://hadoop.apache.org/bylaws.html>
>> > document:
>> >
>> > ===
>> >
>> > 1. In the "Decision Making" : "Actions" section of the Bylaws, the
>> > following text is removed:
>> >
>> > ** Release Plan*
>> >
>> > Defines the timetable and actions for a release. The plan also nominates
>> a
>> > Release Manager.
>> >
>> > Lazy majority of active committers
>> >
>> >
>> > 2. In the "Roles and Responsibilities" section of the Bylaws, an
>> additional
>> > role is defined:
>> >
>> > ** Release Manager*
>> >
>> > A Release Manager (RM) is a committer who volunteers to produce a Release
>> > Candidate according to
>> > HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
>> > The RM shall publish a Release Plan on the *common-dev@* list stating
>> the
>> > branch from which they intend to make a Release Candidate, at least one
>> > week before they do so. The RM is responsible for building consensus
>> around
>> > the content of the Release Candidate, in order to achieve a successful
>> > Product Release vote.
>> >
>> > ===
>> >
>> > Please share your views.
>> > Best regards,
>> > --Matt (long-time release manager)
>>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Chris Nauroth <cn...@hortonworks.com>.
+1 (non-binding)
Chris Nauroth
Hortonworks
http://hortonworks.com/
On Wed, May 22, 2013 at 7:58 AM, Tom White <to...@cloudera.com> wrote:
> +1
>
> Cheers,
> Tom
>
> On Tue, May 21, 2013 at 10:10 PM, Matt Foley <ma...@apache.org> wrote:
> > Hi all,
> > This has been a side topic in several email threads recently. Currently
> we
> > have an ambiguity. We have a tradition in the dev community that any
> > committer can create a branch, and propose release candidates from it.
> Yet
> > the Hadoop bylaws say that releases have to be planned in advance, the
> plan
> > needs to be voted on, and presumably can be denied.
> >
> > Apache policies (primarily here <http://www.apache.org/dev/release.html>
> > and here <http://www.apache.org/foundation/voting.html>, with
> > non-normative commentary
> > here<
> http://incubator.apache.org/guides/releasemanagement.html#best-practice>)
> > are very clear on how Releases have to be approved, and our bylaws are
> > consistent with those policies. But Apache policies don't say anything
> > I've found about Release Plans, nor about voting on Release Plans.
> >
> > I propose the following change, to remove Release Plan votes, and give a
> > simple definition of Release Manager role. I'm opening discussion with
> > this proposal, and will put it to a vote if we seem to be getting
> > consensus. Here's the changes I suggest in the
> > Bylaws<http://hadoop.apache.org/bylaws.html>
> > document:
> >
> > ===
> >
> > 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> > following text is removed:
> >
> > ** Release Plan*
> >
> > Defines the timetable and actions for a release. The plan also nominates
> a
> > Release Manager.
> >
> > Lazy majority of active committers
> >
> >
> > 2. In the "Roles and Responsibilities" section of the Bylaws, an
> additional
> > role is defined:
> >
> > ** Release Manager*
> >
> > A Release Manager (RM) is a committer who volunteers to produce a Release
> > Candidate according to
> > HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> > The RM shall publish a Release Plan on the *common-dev@* list stating
> the
> > branch from which they intend to make a Release Candidate, at least one
> > week before they do so. The RM is responsible for building consensus
> around
> > the content of the Release Candidate, in order to achieve a successful
> > Product Release vote.
> >
> > ===
> >
> > Please share your views.
> > Best regards,
> > --Matt (long-time release manager)
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Tom White <to...@cloudera.com>.
+1
Cheers,
Tom
On Tue, May 21, 2013 at 10:10 PM, Matt Foley <ma...@apache.org> wrote:
> Hi all,
> This has been a side topic in several email threads recently. Currently we
> have an ambiguity. We have a tradition in the dev community that any
> committer can create a branch, and propose release candidates from it. Yet
> the Hadoop bylaws say that releases have to be planned in advance, the plan
> needs to be voted on, and presumably can be denied.
>
> Apache policies (primarily here <http://www.apache.org/dev/release.html>
> and here <http://www.apache.org/foundation/voting.html>, with
> non-normative commentary
> here<http://incubator.apache.org/guides/releasemanagement.html#best-practice>)
> are very clear on how Releases have to be approved, and our bylaws are
> consistent with those policies. But Apache policies don't say anything
> I've found about Release Plans, nor about voting on Release Plans.
>
> I propose the following change, to remove Release Plan votes, and give a
> simple definition of Release Manager role. I'm opening discussion with
> this proposal, and will put it to a vote if we seem to be getting
> consensus. Here's the changes I suggest in the
> Bylaws<http://hadoop.apache.org/bylaws.html>
> document:
>
> ===
>
> 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> following text is removed:
>
> ** Release Plan*
>
> Defines the timetable and actions for a release. The plan also nominates a
> Release Manager.
>
> Lazy majority of active committers
>
>
> 2. In the "Roles and Responsibilities" section of the Bylaws, an additional
> role is defined:
>
> ** Release Manager*
>
> A Release Manager (RM) is a committer who volunteers to produce a Release
> Candidate according to
> HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> The RM shall publish a Release Plan on the *common-dev@* list stating the
> branch from which they intend to make a Release Candidate, at least one
> week before they do so. The RM is responsible for building consensus around
> the content of the Release Candidate, in order to achieve a successful
> Product Release vote.
>
> ===
>
> Please share your views.
> Best regards,
> --Matt (long-time release manager)
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Alejandro Abdelnur <tu...@cloudera.com>.
+1
On Tue, May 21, 2013 at 2:48 PM, Suresh Srinivas <su...@hortonworks.com>wrote:
> +1
>
>
> On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
>
> > Hi all,
> > This has been a side topic in several email threads recently. Currently
> we
> > have an ambiguity. We have a tradition in the dev community that any
> > committer can create a branch, and propose release candidates from it.
> Yet
> > the Hadoop bylaws say that releases have to be planned in advance, the
> plan
> > needs to be voted on, and presumably can be denied.
> >
> > Apache policies (primarily here <http://www.apache.org/dev/release.html>
> > and here <http://www.apache.org/foundation/voting.html>, with
> > non-normative commentary
> > here<
> > http://incubator.apache.org/guides/releasemanagement.html#best-practice
> >)
> > are very clear on how Releases have to be approved, and our bylaws are
> > consistent with those policies. But Apache policies don't say anything
> > I've found about Release Plans, nor about voting on Release Plans.
> >
> > I propose the following change, to remove Release Plan votes, and give a
> > simple definition of Release Manager role. I'm opening discussion with
> > this proposal, and will put it to a vote if we seem to be getting
> > consensus. Here's the changes I suggest in the
> > Bylaws<http://hadoop.apache.org/bylaws.html>
> > document:
> >
> > ===
> >
> > 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> > following text is removed:
> >
> > ** Release Plan*
> >
> > Defines the timetable and actions for a release. The plan also nominates
> a
> > Release Manager.
> >
> > Lazy majority of active committers
> >
> >
> > 2. In the "Roles and Responsibilities" section of the Bylaws, an
> additional
> > role is defined:
> >
> > ** Release Manager*
> >
> > A Release Manager (RM) is a committer who volunteers to produce a Release
> > Candidate according to
> > HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> > The RM shall publish a Release Plan on the *common-dev@* list stating
> the
> > branch from which they intend to make a Release Candidate, at least one
> > week before they do so. The RM is responsible for building consensus
> around
> > the content of the Release Candidate, in order to achieve a successful
> > Product Release vote.
> >
> > ===
> >
> > Please share your views.
> > Best regards,
> > --Matt (long-time release manager)
> >
>
>
>
> --
> http://hortonworks.com/download/
>
--
Alejandro
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Suresh Srinivas <su...@hortonworks.com>.
+1
On Tue, May 21, 2013 at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
> Hi all,
> This has been a side topic in several email threads recently. Currently we
> have an ambiguity. We have a tradition in the dev community that any
> committer can create a branch, and propose release candidates from it. Yet
> the Hadoop bylaws say that releases have to be planned in advance, the plan
> needs to be voted on, and presumably can be denied.
>
> Apache policies (primarily here <http://www.apache.org/dev/release.html>
> and here <http://www.apache.org/foundation/voting.html>, with
> non-normative commentary
> here<
> http://incubator.apache.org/guides/releasemanagement.html#best-practice>)
> are very clear on how Releases have to be approved, and our bylaws are
> consistent with those policies. But Apache policies don't say anything
> I've found about Release Plans, nor about voting on Release Plans.
>
> I propose the following change, to remove Release Plan votes, and give a
> simple definition of Release Manager role. I'm opening discussion with
> this proposal, and will put it to a vote if we seem to be getting
> consensus. Here's the changes I suggest in the
> Bylaws<http://hadoop.apache.org/bylaws.html>
> document:
>
> ===
>
> 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> following text is removed:
>
> ** Release Plan*
>
> Defines the timetable and actions for a release. The plan also nominates a
> Release Manager.
>
> Lazy majority of active committers
>
>
> 2. In the "Roles and Responsibilities" section of the Bylaws, an additional
> role is defined:
>
> ** Release Manager*
>
> A Release Manager (RM) is a committer who volunteers to produce a Release
> Candidate according to
> HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> The RM shall publish a Release Plan on the *common-dev@* list stating the
> branch from which they intend to make a Release Candidate, at least one
> week before they do so. The RM is responsible for building consensus around
> the content of the Release Candidate, in order to achieve a successful
> Product Release vote.
>
> ===
>
> Please share your views.
> Best regards,
> --Matt (long-time release manager)
>
--
http://hortonworks.com/download/
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Arpit Gupta <ar...@hortonworks.com>.
+1
--
Arpit Gupta
Hortonworks Inc.
http://hortonworks.com/
On May 21, 2013, at 2:10 PM, Matt Foley <ma...@apache.org> wrote:
> Hi all,
> This has been a side topic in several email threads recently. Currently we
> have an ambiguity. We have a tradition in the dev community that any
> committer can create a branch, and propose release candidates from it. Yet
> the Hadoop bylaws say that releases have to be planned in advance, the plan
> needs to be voted on, and presumably can be denied.
>
> Apache policies (primarily here <http://www.apache.org/dev/release.html>
> and here <http://www.apache.org/foundation/voting.html>, with
> non-normative commentary
> here<http://incubator.apache.org/guides/releasemanagement.html#best-practice>)
> are very clear on how Releases have to be approved, and our bylaws are
> consistent with those policies. But Apache policies don't say anything
> I've found about Release Plans, nor about voting on Release Plans.
>
> I propose the following change, to remove Release Plan votes, and give a
> simple definition of Release Manager role. I'm opening discussion with
> this proposal, and will put it to a vote if we seem to be getting
> consensus. Here's the changes I suggest in the
> Bylaws<http://hadoop.apache.org/bylaws.html>
> document:
>
> ===
>
> 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> following text is removed:
>
> ** Release Plan*
>
> Defines the timetable and actions for a release. The plan also nominates a
> Release Manager.
>
> Lazy majority of active committers
>
>
> 2. In the "Roles and Responsibilities" section of the Bylaws, an additional
> role is defined:
>
> ** Release Manager*
>
> A Release Manager (RM) is a committer who volunteers to produce a Release
> Candidate according to
> HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> The RM shall publish a Release Plan on the *common-dev@* list stating the
> branch from which they intend to make a Release Candidate, at least one
> week before they do so. The RM is responsible for building consensus around
> the content of the Release Candidate, in order to achieve a successful
> Product Release vote.
>
> ===
>
> Please share your views.
> Best regards,
> --Matt (long-time release manager)
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Steve Loughran <st...@hortonworks.com>.
+1 (committer vote; not sure if it is binding on this or not)
RE: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Jagane Sundar <ja...@sundar.org>.
Thanks for highlighting my concern, Matt.
I do not profess to great wisdom in the mechanisms of planning for, developing and putting out stable releases of Hadoop.
My point of view is quite simple, and pardon me for stating the obvious: A thriving Hadoop community is more that the developers of core HDFS and YARN - it includes the users of Hadoop, it includes the developers who write applications for Hadoop, it includes projects such as HBase that build on top of Hadoop, it includes commercial vendors who package Hadoop as part of their Big Data solutions, it includes vendors such as ourselves who build proprietary functionality on top of Hadoop, it includes OS vendors who want to bundle Hadoop as part of their Operating Systems.
Again - stating the obvious: For such a community to thrive and grow, a limited number of stable releases, along with a limited number of development branches where strong multi-company development takes place is crucial. There are a number of alternative technologies such as riak, mongoDB, memcache, MapR, etc. that are well funded and eager to overtake Hadoop, should Hadoop fragment.
Hopefully, the collective wisdom of the Hadoop PMC will play the benevolent dictator role that Linus plays so well for Linux.
I will stop here, since nobody ever reads more than four sentences of any email....
Jagane
-----Original Message-----
From: Matt Foley [mailto:mfoley@hortonworks.com]
Sent: Wednesday, May 22, 2013 12:51 PM
To: common-dev@hadoop.apache.org
Subject: Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Hi Jagane,
My response to your concerns is that I hope the PMC will have enough wisdom not to pass votes for a confusing number of releases -- if only to avoid the kind of fragmentation you point out could happen.
To date, however, this does not seem to have been a major problem in our community. Indeed, lack of regularity in release schedules is more often cited as a problem. (Which this amendment is orthogonal to, so please start a different discussion thread if anyone wants to get into that issue! :-)
Thanks,
--Matt
On Wed, May 22, 2013 at 3:52 AM, Steve Loughran <st...@hortonworks.com>wrote:
> On 21 May 2013 23:47, Jagane Sundar <ja...@sundar.org> wrote:
>
> > I see one significant benefit to having Release Plan votes: Fewer
> releases
> > with more members of the community working on any given release.
> > In turn, fewer Hadoop releases implies less confusion for end users
> > attempting to download and use an Apache Hadoop release.
> >
> > If there are a dozen different releases of Apache Hadoop available
> > for download at the Apache Hadoop website, end users will go to a
> > commercial vendor packaged version of Hadoop. That is not good for
> > the Apache Hadoop community as a whole.
> >
> > Jagane
> >
>
> I agree we don't want fragmentation; you don't want to have to choose
> between hadoop-2.1, hadoop-2.1.stevel-may and hadoop-2.1.stevel-june.
>
> With a vote on artifact releases, this can be prevented. I am free to
> create my -may and -june artifacts, but the PMC -it is just the PMC
> right?- get to say "no steve, you can't ship this from the apache.org"
> site, though I am free to make my own (which I have done in the past &
> put into my own RPMs. No need for a vote if I do it on my own site,
> though I did make sure I named the JARs and RPMs something else so
> that maven builds didn't get confused.
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Matt Foley <mf...@hortonworks.com>.
Hi Jagane,
My response to your concerns is that I hope the PMC will have enough wisdom
not to pass votes for a confusing number of releases -- if only to avoid
the kind of fragmentation you point out could happen.
To date, however, this does not seem to have been a major problem in our
community. Indeed, lack of regularity in release schedules is more often
cited as a problem. (Which this amendment is orthogonal to, so please start
a different discussion thread if anyone wants to get into that issue! :-)
Thanks,
--Matt
On Wed, May 22, 2013 at 3:52 AM, Steve Loughran <st...@hortonworks.com>wrote:
> On 21 May 2013 23:47, Jagane Sundar <ja...@sundar.org> wrote:
>
> > I see one significant benefit to having Release Plan votes: Fewer
> releases
> > with more members of the community working on any given release.
> > In turn, fewer Hadoop releases implies less confusion for end users
> > attempting to download and use an Apache Hadoop release.
> >
> > If there are a dozen different releases of Apache Hadoop available for
> > download at the Apache Hadoop website, end users will go to a commercial
> > vendor packaged version of Hadoop. That is not good for the Apache Hadoop
> > community as a whole.
> >
> > Jagane
> >
>
> I agree we don't want fragmentation; you don't want to have to choose
> between hadoop-2.1, hadoop-2.1.stevel-may and hadoop-2.1.stevel-june.
>
> With a vote on artifact releases, this can be prevented. I am free to
> create my -may and -june artifacts, but the PMC -it is just the PMC right?-
> get to say "no steve, you can't ship this from the apache.org" site,
> though
> I am free to make my own (which I have done in the past & put into my own
> RPMs. No need for a vote if I do it on my own site, though I did make sure
> I named the JARs and RPMs something else so that maven builds didn't get
> confused.
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Steve Loughran <st...@hortonworks.com>.
On 21 May 2013 23:47, Jagane Sundar <ja...@sundar.org> wrote:
> I see one significant benefit to having Release Plan votes: Fewer releases
> with more members of the community working on any given release.
> In turn, fewer Hadoop releases implies less confusion for end users
> attempting to download and use an Apache Hadoop release.
>
> If there are a dozen different releases of Apache Hadoop available for
> download at the Apache Hadoop website, end users will go to a commercial
> vendor packaged version of Hadoop. That is not good for the Apache Hadoop
> community as a whole.
>
> Jagane
>
I agree we don't want fragmentation; you don't want to have to choose
between hadoop-2.1, hadoop-2.1.stevel-may and hadoop-2.1.stevel-june.
With a vote on artifact releases, this can be prevented. I am free to
create my -may and -june artifacts, but the PMC -it is just the PMC right?-
get to say "no steve, you can't ship this from the apache.org" site, though
I am free to make my own (which I have done in the past & put into my own
RPMs. No need for a vote if I do it on my own site, though I did make sure
I named the JARs and RPMs something else so that maven builds didn't get
confused.
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Matt Foley <ma...@apache.org>.
Hi Jagane,
since you did not explicitly cast a -1 or other numerical vote, please if
you wish go ahead and cast a vote in the VOTE thread.
Best regards,
--Matt
On Tue, May 21, 2013 at 3:47 PM, Jagane Sundar <ja...@sundar.org> wrote:
> I see one significant benefit to having Release Plan votes: Fewer releases
> with more members of the community working on any given release.
> In turn, fewer Hadoop releases implies less confusion for end users
> attempting to download and use an Apache Hadoop release.
>
> If there are a dozen different releases of Apache Hadoop available for
> download at the Apache Hadoop website, end users will go to a commercial
> vendor packaged version of Hadoop. That is not good for the Apache Hadoop
> community as a whole.
>
> Jagane
>
RE: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Jagane Sundar <ja...@sundar.org>.
I see one significant benefit to having Release Plan votes: Fewer releases with more members of the community working on any given release.
In turn, fewer Hadoop releases implies less confusion for end users attempting to download and use an Apache Hadoop release.
If there are a dozen different releases of Apache Hadoop available for download at the Apache Hadoop website, end users will go to a commercial vendor packaged version of Hadoop. That is not good for the Apache Hadoop community as a whole.
Jagane
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Ravi Sharma <ra...@gmail.com>.
+1
On Wed, May 22, 2013 at 7:37 PM, Jonathan Eagles <je...@gmail.com> wrote:
> +1
>
>
> On Tue, May 21, 2013 at 4:10 PM, Matt Foley <ma...@apache.org> wrote:
>
> > Hi all,
> > This has been a side topic in several email threads recently. Currently
> we
> > have an ambiguity. We have a tradition in the dev community that any
> > committer can create a branch, and propose release candidates from it.
> Yet
> > the Hadoop bylaws say that releases have to be planned in advance, the
> plan
> > needs to be voted on, and presumably can be denied.
> >
> > Apache policies (primarily here <http://www.apache.org/dev/release.html>
> > and here <http://www.apache.org/foundation/voting.html>, with
> > non-normative commentary
> > here<
> > http://incubator.apache.org/guides/releasemanagement.html#best-practice
> >)
> > are very clear on how Releases have to be approved, and our bylaws are
> > consistent with those policies. But Apache policies don't say anything
> > I've found about Release Plans, nor about voting on Release Plans.
> >
> > I propose the following change, to remove Release Plan votes, and give a
> > simple definition of Release Manager role. I'm opening discussion with
> > this proposal, and will put it to a vote if we seem to be getting
> > consensus. Here's the changes I suggest in the
> > Bylaws<http://hadoop.apache.org/bylaws.html>
> > document:
> >
> > ===
> >
> > 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> > following text is removed:
> >
> > ** Release Plan*
> >
> > Defines the timetable and actions for a release. The plan also nominates
> a
> > Release Manager.
> >
> > Lazy majority of active committers
> >
> >
> > 2. In the "Roles and Responsibilities" section of the Bylaws, an
> additional
> > role is defined:
> >
> > ** Release Manager*
> >
> > A Release Manager (RM) is a committer who volunteers to produce a Release
> > Candidate according to
> > HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> > The RM shall publish a Release Plan on the *common-dev@* list stating
> the
> > branch from which they intend to make a Release Candidate, at least one
> > week before they do so. The RM is responsible for building consensus
> around
> > the content of the Release Candidate, in order to achieve a successful
> > Product Release vote.
> >
> > ===
> >
> > Please share your views.
> > Best regards,
> > --Matt (long-time release manager)
> >
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by Jonathan Eagles <je...@gmail.com>.
+1
On Tue, May 21, 2013 at 4:10 PM, Matt Foley <ma...@apache.org> wrote:
> Hi all,
> This has been a side topic in several email threads recently. Currently we
> have an ambiguity. We have a tradition in the dev community that any
> committer can create a branch, and propose release candidates from it. Yet
> the Hadoop bylaws say that releases have to be planned in advance, the plan
> needs to be voted on, and presumably can be denied.
>
> Apache policies (primarily here <http://www.apache.org/dev/release.html>
> and here <http://www.apache.org/foundation/voting.html>, with
> non-normative commentary
> here<
> http://incubator.apache.org/guides/releasemanagement.html#best-practice>)
> are very clear on how Releases have to be approved, and our bylaws are
> consistent with those policies. But Apache policies don't say anything
> I've found about Release Plans, nor about voting on Release Plans.
>
> I propose the following change, to remove Release Plan votes, and give a
> simple definition of Release Manager role. I'm opening discussion with
> this proposal, and will put it to a vote if we seem to be getting
> consensus. Here's the changes I suggest in the
> Bylaws<http://hadoop.apache.org/bylaws.html>
> document:
>
> ===
>
> 1. In the "Decision Making" : "Actions" section of the Bylaws, the
> following text is removed:
>
> ** Release Plan*
>
> Defines the timetable and actions for a release. The plan also nominates a
> Release Manager.
>
> Lazy majority of active committers
>
>
> 2. In the "Roles and Responsibilities" section of the Bylaws, an additional
> role is defined:
>
> ** Release Manager*
>
> A Release Manager (RM) is a committer who volunteers to produce a Release
> Candidate according to
> HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> The RM shall publish a Release Plan on the *common-dev@* list stating the
> branch from which they intend to make a Release Candidate, at least one
> week before they do so. The RM is responsible for building consensus around
> the content of the Release Candidate, in order to achieve a successful
> Product Release vote.
>
> ===
>
> Please share your views.
> Best regards,
> --Matt (long-time release manager)
>
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.
+1million
I completely agree with Chris D's separate email too about not
vote'ing about intentions, and voting on actual artifacts.
The fact of the matter at the ASF is that any PMC member; heck any
contributor can roll a release candidate. If that candidate receives
at least 3 PMC member +1s (to make it binding as backed by the Foundation
and its distributed committees and structure), and more +1s than -1s,
you've got yourself
a release. It's up to someone on the PMC/committee at that point to publish
the bits on ASF infrastructure and ultimately to make sure that whoever
made
the RC has a key that's present in a KEYS file or on id.apache.org, but
beyond that, that's it.*
Cheers,
Chris
* - if Joe Schmoe comes along and makes a release candidate that passes
muster with the Hadoop PMC, then I would expect Joe Schmoe should be added
to the PMC :)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message-----
From: Matt Foley <ma...@apache.org>
Reply-To: "common-dev@hadoop.apache.org" <co...@hadoop.apache.org>,
"mattf@apache.org" <ma...@apache.org>
Date: Tuesday, May 21, 2013 2:10 PM
To: "common-dev@hadoop.apache.org" <co...@hadoop.apache.org>
Subject: [PROPOSAL] change in bylaws to remove Release Plan vote
>Hi all,
>This has been a side topic in several email threads recently. Currently
>we
>have an ambiguity. We have a tradition in the dev community that any
>committer can create a branch, and propose release candidates from it.
>Yet
>the Hadoop bylaws say that releases have to be planned in advance, the
>plan
>needs to be voted on, and presumably can be denied.
>
>Apache policies (primarily here <http://www.apache.org/dev/release.html>
> and here <http://www.apache.org/foundation/voting.html>, with
>non-normative commentary
>here<http://incubator.apache.org/guides/releasemanagement.html#best-practi
>ce>)
>are very clear on how Releases have to be approved, and our bylaws are
>consistent with those policies. But Apache policies don't say anything
>I've found about Release Plans, nor about voting on Release Plans.
>
>I propose the following change, to remove Release Plan votes, and give a
>simple definition of Release Manager role. I'm opening discussion with
>this proposal, and will put it to a vote if we seem to be getting
>consensus. Here's the changes I suggest in the
>Bylaws<http://hadoop.apache.org/bylaws.html>
> document:
>
>===
>
>1. In the "Decision Making" : "Actions" section of the Bylaws, the
>following text is removed:
>
>** Release Plan*
>
>Defines the timetable and actions for a release. The plan also nominates a
>Release Manager.
>
>Lazy majority of active committers
>
>
>2. In the "Roles and Responsibilities" section of the Bylaws, an
>additional
>role is defined:
>
>** Release Manager*
>
>A Release Manager (RM) is a committer who volunteers to produce a Release
>Candidate according to
>HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> The RM shall publish a Release Plan on the *common-dev@* list stating the
>branch from which they intend to make a Release Candidate, at least one
>week before they do so. The RM is responsible for building consensus
>around
>the content of the Release Candidate, in order to achieve a successful
>Product Release vote.
>
>===
>
>Please share your views.
>Best regards,
>--Matt (long-time release manager)
Re: [PROPOSAL] change in bylaws to remove Release Plan vote
Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.
+1million
I completely agree with Chris D's separate email too about not
vote'ing about intentions, and voting on actual artifacts.
The fact of the matter at the ASF is that any PMC member; heck any
contributor can roll a release candidate. If that candidate receives
at least 3 PMC member +1s (to make it binding as backed by the Foundation
and its distributed committees and structure), and more +1s than -1s,
you've got yourself
a release. It's up to someone on the PMC/committee at that point to publish
the bits on ASF infrastructure and ultimately to make sure that whoever
made
the RC has a key that's present in a KEYS file or on id.apache.org, but
beyond that, that's it.*
Cheers,
Chris
* - if Joe Schmoe comes along and makes a release candidate that passes
muster with the Hadoop PMC, then I would expect Joe Schmoe should be added
to the PMC :)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message-----
From: Matt Foley <ma...@apache.org>
Reply-To: "common-dev@hadoop.apache.org" <co...@hadoop.apache.org>,
"mattf@apache.org" <ma...@apache.org>
Date: Tuesday, May 21, 2013 2:10 PM
To: "common-dev@hadoop.apache.org" <co...@hadoop.apache.org>
Subject: [PROPOSAL] change in bylaws to remove Release Plan vote
>Hi all,
>This has been a side topic in several email threads recently. Currently
>we
>have an ambiguity. We have a tradition in the dev community that any
>committer can create a branch, and propose release candidates from it.
>Yet
>the Hadoop bylaws say that releases have to be planned in advance, the
>plan
>needs to be voted on, and presumably can be denied.
>
>Apache policies (primarily here <http://www.apache.org/dev/release.html>
> and here <http://www.apache.org/foundation/voting.html>, with
>non-normative commentary
>here<http://incubator.apache.org/guides/releasemanagement.html#best-practi
>ce>)
>are very clear on how Releases have to be approved, and our bylaws are
>consistent with those policies. But Apache policies don't say anything
>I've found about Release Plans, nor about voting on Release Plans.
>
>I propose the following change, to remove Release Plan votes, and give a
>simple definition of Release Manager role. I'm opening discussion with
>this proposal, and will put it to a vote if we seem to be getting
>consensus. Here's the changes I suggest in the
>Bylaws<http://hadoop.apache.org/bylaws.html>
> document:
>
>===
>
>1. In the "Decision Making" : "Actions" section of the Bylaws, the
>following text is removed:
>
>** Release Plan*
>
>Defines the timetable and actions for a release. The plan also nominates a
>Release Manager.
>
>Lazy majority of active committers
>
>
>2. In the "Roles and Responsibilities" section of the Bylaws, an
>additional
>role is defined:
>
>** Release Manager*
>
>A Release Manager (RM) is a committer who volunteers to produce a Release
>Candidate according to
>HowToRelease<https://wiki.apache.org/hadoop/HowToRelease>.
> The RM shall publish a Release Plan on the *common-dev@* list stating the
>branch from which they intend to make a Release Candidate, at least one
>week before they do so. The RM is responsible for building consensus
>around
>the content of the Release Candidate, in order to achieve a successful
>Product Release vote.
>
>===
>
>Please share your views.
>Best regards,
>--Matt (long-time release manager)