Allen, to be clear, I am not against any branch release effort here. However,
as RM for previous releases 2.6.3 and 2.6.4, I feel to have responsibility to
take care branch-2.6 together with other RMs (Vinod and Sangjin) on this branch
and understand current gap - especially, to get consensus from community on the
future plan for 2.6.x.
Our bylaw give us freedom for anyone to do release effort, but our bylaw
doesn't stop our rights for reasonable question/concern on any release plan. As
you mentioned below, people can potentially fire up branch-1 release effort.
But if you call a release plan tomorrow for branch-1, I cannot imagine nobody
will question on that effort. Isn't it?
Let's keep discussions on releasing 2.6.5 more technical. IMO, to make 2.6.5
release more reasonable, shouldn't we check following questions first?
1. Do we have any significant issues that should land on 2.6.5 comparing with
2.6.4?
2. If so, any technical reasons (like: upgrade is not smoothly, performance
downgrade, incompatibility with downstream projects, etc.) to stop our users to
move from 2.6.4 to 2.7.2/2.7.3?
I believe having good answer on these questions can make our release plan more
reasonable to the whole community. More thoughts?
Thanks,
Junping
________________________________________
From: Allen Wittenauer <a...@effectivemachines.com>
Sent: Thursday, August 11, 2016 3:13 PM
To: Junping Du
Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org;
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Release thread] 2.6.5 release activities
> On Aug 11, 2016, at 5:59 AM, Junping Du <j...@hortonworks.com> wrote:
>
> These comments are more like wishes but not giving more clarifications
> on the needs. I would like to hear more specific reasons to not move to 2.7.x
> releases but prefer to upgrade to 2.6.5. If the only reason is about
> expectation management, I think we should claim 2.6.5 is the last branch-2.6
> release after this release work, otherwise people would expect us to maintain
> this branch forever which is impossible and unnecessary. Thoughts?
The bylaws[*] are such that if community members want to spend their
time working on a branch, there isn't much to prevent that other than the PMC
voting down the release of that branch or removing the committers working on
that branch. As has been pointed out to me many times, one can't dictate where
others spend their volunteer time. If they want to spend their efforts on
branch-2.6, they can. If that comes at the detriment of releases around
branch-2.7 or branch-2.8 or even trunk, then so be it. Technically, someone
could still fire up a branch-1 release. Given the numbers of committers and
PMC members as listed on the main ASF website (not the list on project one), we
should have more than enough people to do all this work anyway.
* - of course, there's a few bylaws that aren't really enforced, so maybe even
this isn't true?
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
