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 wrote: > > > On Jan

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 release cadence, > co

Re: [VOTE] Release cadence and EOL

;> start >> >> 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 pa

Re: [VOTE] Release cadence and EOL

rt. 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 target release and her/his > own > >> interest rele

Re: [VOTE] Release cadence and EOL

h I conservatively agree 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 people and could >> s

Re: [VOTE] Release cadence and EOL

Thanks, > > Junping > ________ > From: Allen Wittenauer > Sent: Wednesday, January 18, 2017 3:30 PM > To: Chris Trezzo > Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; > yarn-...@hadoop.apache.org; mapreduce-...@hadoop

Re: [VOTE] Release cadence and EOL

..@hadoop.apache.org; hdfs-dev@hadoop.apache.org; yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org Subject: 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 quest

Re: [VOTE] Release cadence and EOL

think we should discuss separately. Thanks, Junping From: Allen Wittenauer Sent: Wednesday, January 18, 2017 3:30 PM To: Chris Trezzo Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.or

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 universe is with new rel

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 longer

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 mino

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 ( https://s