hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 俊平堵 <junping...@apache.org>
Subject Re: [DISCUSSION] Release Plan for Apache Hadoop 2.6.4
Date Mon, 18 Jan 2016 02:32:49 GMT
Thanks Akira and Eric for the feedback and help here. Our gap between
target commits (http://s.apache.org/JpE) and fixed commits (
http://s.apache.org/vJB) are much smaller now (from 37 to 15) for 2.6.4 in
passed week due to everyone's hard work.
I hope we can reduce the gap to be 0 in the coming week. In the mean while,
the branch out effort for 2.6.4 will wait for vote result of 2.7.2 for the
next step.

Cheers,

Junping

2016-01-08 7:55 GMT+00:00 Akira AJISAKA <ajisakaa@oss.nttdata.co.jp>:

> +1 for releasing 2.6.4 after release 2.7.2.
> I'll work on the list [2].
>
> Thanks,
> Akira
>
>
> On 1/7/16 08:59, Junping Du wrote:
>
>> Hello folks,
>>         Hope everyone had a wonderful holiday and good rest in passed
>> weeks. We just had a 2.6.3 release on Dec.17 and now it is a good time to
>> look forward to the next branch-2.6 maintenance release - 2.6.4 in the
>> beginning of new year. As usual, this release will be based on latest
>> release 2.6.3 but include a couple of critical/blocker bug fixes that
>> identified in community recently.
>>
>> Things Done/TODO:
>>
>>    + Schedule
>>      -- According to previous email discussion thread in community, we
>> are prefering fast-moving way (roughly as monthly) of releasing fixes on
>> branch-2.6. So I would expect this release could happen around end of Jan.
>> or early of Feb. dependens on if RC & VOTE process going on smoothly. Also,
>> it should be after release 2.7.2 to get rid of any possible disturb to that
>> release.
>>
>>    + Branch
>>      -- 2.6.4 will be based on branch-2.6, which has been open to 2.6.4
>> commits for a while. I plan to branch out branch-2.6.4 sometime next week
>> according to status of target/fixed fixes.
>>      -- Before 2.6.4 branch is cut off, new commits coming as fix to
>> 2.6.4 is good to commit/merge to trunk, branch-2 and branch-2.6.
>>
>>    + Patches
>>      -- In last couple of days, I went through all critial/blocker bug
>> fixes in the coming 2.7.2 release and ping authors/committers on JIRA to
>> ask for the same effort on branch-2.6.4. I could do more rounds of the same
>> practice in case I could miss something helpful. Also, a kindly reminder
>> from original author and committer is also appreciated.
>>      -- So far, 2.6.4 already has 18 fixes as list of [1] shows. However,
>> there are totally 55 fixes target for 2.6.4 for now [2], so there is still
>> a large gap and we need to work harder to resolve these tickets as many as
>> we can and push out some non-critical ones to meet our promise of date.
>>
>>    + Release
>>      -- Still too early to do anything directly related to RC. Will work
>> on resolve fixes in list of [2] first, and appreciate any help on this
>> effort.
>>
>> Any thoughts? Especially on schedule and list of patches that should be
>> included?
>>
>>
>> Cheers,
>>
>> Junping
>>
>> [1] Tickets fixed in 2.6.4:
>> http://s.apache.org/vJB
>>
>> [2] Tickets targets for 2.6.4:
>> http://s.apache.org/JpE
>>
>>
>> ________________________________________
>> From: Junping Du
>> Sent: Thursday, December 17, 2015 1:36 PM
>> To: common-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
>> Cc: hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org;
>> junping_du@apache.org
>> Subject: [RESULT] [VOTE] Release Apache Hadoop 2.6.3 RC0
>>
>> Hi all in community,
>>       I give my binding +1 to close the vote for 2.6.3 RC0. With 18 +1s
>> (10 binding), one +0 (non-binding) and no -1s, the vote passes.
>>
>> Thanks for everyone who tried the release candidate and voted. Thanks
>> Vinod, Sangjin and Steve to provide me advices on release process.
>>
>> I'll push the release bits and send out an announcement for 2.6.3 soon.
>>
>> Cheers,
>>
>> Junping
>> ________________________________________
>> From: Xuan Gong <xgong@hortonworks.com>
>> Sent: Thursday, December 17, 2015 12:29 AM
>> To: common-dev@hadoop.apache.org
>> Cc: hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org;
>> yarn-dev@hadoop.apache.org; junping_du@apache.org
>> Subject: Re: [VOTE] Release Apache Hadoop 2.6.3 RC0
>>
>> +1 (binding),
>>
>> Build and deploy the cluster from source code.
>> Ran a few example jobs and passed successfully.
>>
>> Xuan Gong
>>
>> On Dec 16, 2015, at 4:07 PM, Arpit Agarwal <aagarwal@hortonworks.com>
>>> wrote:
>>>
>>> +1 (binding)
>>>
>>> - Verified signatures for source and binary distributions
>>> - Built jars from source with java 1.7.0_79
>>> - Deployed single-node pseudo-cluster
>>> - Ran example map reduce jobs
>>> - Ran hdfs admin commands, verified NN web UI shows expected usages
>>>
>>>
>>>
>>> On 12/11/15, 4:16 PM, "Junping Du" <jdu@hortonworks.com> wrote:
>>>
>>>
>>>> Hi all developers in hadoop community,
>>>>   I've created a release candidate RC0 for Apache Hadoop 2.6.3 (the
>>>> next maintenance release to follow up 2.6.2.) according to email thread of
>>>> release plan 2.6.3 [1]. Sorry for this RC coming a bit late as several
>>>> blocker issues were getting committed until yesterday. Below is the details:
>>>>
>>>> The RC is available for validation at:
>>>> *http://people.apache.org/~junping_du/hadoop-2.6.3-RC0/
>>>> <http://people.apache.org/~junping_du/hadoop-2.6.3-RC0/>*
>>>>
>>>> The RC tag in git is: release-2.6.3-RC0
>>>>
>>>> The maven artifacts are staged via repository.apache.org at:
>>>> *
>>>> https://repository.apache.org/content/repositories/orgapachehadoop-1025/
>>>> ?
>>>> <
>>>> https://repository.apache.org/content/repositories/orgapachehadoop-1025/
>>>> >*
>>>>
>>>> You can find my public key at:
>>>> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS
>>>>
>>>> Please try the release and vote. The vote will run for the usual 5 days.
>>>>
>>>> Thanks and happy weekend!
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Junping
>>>>
>>>>
>>>> [1]: 2.6.3 release plan: http://markmail.org/thread/nc2jogbgni37vu6y
>>>>
>>>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message