Re: [VOTE] Release cadence and EOL

I'm going to stop the vote and go back to the discussion. It shouldn't be a big surprise given the reservation we have so far. I do hope there will be some actionable outcome as a result of that discussion. Regards, Sangjin On Mon, Jan 23, 2017 at 8:17 AM, Allen Wittenauer

Re: [VOTE] Release cadence and EOL

> On Jan 21, 2017, at 7:08 PM, Karthik Kambatla wrote: > > 3. RM: some method to madness. Junping, for instance, is trying to roll > a release with 2300 patches. It is a huge time investment. (Thanks again, > Junping.) Smaller releases are easier to manage. A target

Re: [VOTE] Release cadence and EOL

tenance release. > >> >> > >> >> 2. For release effort, apache law claim that committer can > >> >> volunteer > >> >> RM for any release. With this release EOL proposal passes and written > >> >> into > >> >>

Re: [VOTE] Release cadence and EOL

gt; >> release effort. We don't want to waste community time/resource to >> >> verify/vote a narrow interested release. >> >> >> >> 3. About committer's responsibility, I think the bottom line is >> >> committer should commit patch contributor's

Re: [VOTE] Release cadence and EOL

ree with Allen's point that > this > >> vote doesn't change anything. But if a committer want to take care more > >> interest from the whole community like most committers are doing today, > >> he/she should understand which branches can benefit more

Re: [VOTE] Release cadence and EOL

skip some EOL release branches for backport effort. >> >> About major release EOL, this could be more complicated and I think we >> should discuss separately. >> >> Thanks, >> >> Junping >> >>

Re: [VOTE] Release cadence and EOL

> > From: Allen Wittenauer <a...@effectivemachines.com> > Sent: Wednesday, January 18, 2017 3:30 PM > To: Chris Trezzo > Cc: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; > yarn-dev@hadoop.apache.or

Re: [VOTE] Release cadence and EOL

To: Chris Trezzo Cc: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org Subject: Re: [VOTE] Release cadence and EOL > On Jan 18, 2017, at 11:21 AM, Chris Trezzo <ctre...@gmail.com> wrote: > > Thanks

Re: [VOTE] Release cadence and EOL

bject: Re: [VOTE] Release cadence and EOL > On Jan 18, 2017, at 11:21 AM, Chris Trezzo <ctre...@gmail.com> wrote: > > Thanks Sangjin for pushing this forward! I have a few questions: These are great questions, because I know I'm not seeing a whole lot of substance in this

Re: [VOTE] Release cadence and EOL

> On Jan 18, 2017, at 11:21 AM, Chris Trezzo wrote: > > Thanks Sangjin for pushing this forward! I have a few questions: These are great questions, because I know I'm not seeing a whole lot of substance in this vote. The way to EOL software in the open source

Re: [VOTE] Release cadence and EOL

Thanks Sangjin for pushing this forward! I have a few questions: 1. What is the definition of end-of-life for a release in the hadoop project? My current understanding is as follows: When a release line reaches end-of-life, there are no more planned releases for that line. Committers are no

Re: [VOTE] Release cadence and EOL

+1 I would also like to see some process guidelines. I should have brought this up on the discussion thread, but I thought of them only now :( - Is an RM responsible for all maintenance releases against a minor release, or finding another RM to drive a maintenance release? In the past,

Re: [VOTE] Release cadence and EOL

Thanks for correcting me! I left out a sentence by mistake. :) To correct the proposal we're voting for: A minor release on the latest major line should be every 6 months, and a maintenance release on a minor release (as there may be concurrently maintained minor releases) every 2 months. A

Re: [VOTE] Release cadence and EOL

Thanks for driving this, Sangjin. Quick question, though: the subject line is "Release cadence and EOL," but I don't see anything about cadence in the proposal. Did I miss something? Daniel On 1/17/17 8:35 AM, Sangjin Lee wrote: Following up on the discussion thread on this topic (

[VOTE] Release cadence and EOL

Following up on the discussion thread on this topic ( https://s.apache.org/eFOf), I'd like to put the proposal for a vote for the release cadence and EOL. The proposal is as follows: "A minor release line is end-of-lifed 2 years after it is released or there are 2 newer minor releases, whichever