Thanks Sunil.

I try to setup release environment locally following the guide[1]. Will
reach out to you if I meet any issues. Thanks again.

Regards.

[1] https://cwiki.apache.org/confluence/display/HADOOP2/HowToRelease

On Thu, Sep 3, 2020 at 11:57 AM Sunil Govindan <sun...@apache.org> wrote:

> Hi Xiaoqiao,
>
> Thanks for volunteering.
> I could help to guide you through the process.
>
> Thanks,
> Sunil
>
> On Thu, Sep 3, 2020 at 9:09 AM Xiaoqiao He <xq.he2...@gmail.com> wrote:
>
>> Thanks Wei-Chiu for initiating this.
>>
>> It's been nearly a year since Hadoop-3.2.1 released(2019 Sep 22).
>>
>> We have several important fixes landed in branch-3.2 (around 37
>> blockers/critical issues)[1].
>> There are also 3 blockers/critical pending issues and 3 other pending
>> issues on 3.2.2[2].
>>
>> I am willing to volunteer with the Hadoop 3.3.2 release work. Anyone who
>> would like to contribute or offer some suggestions & release guides will
>> be appreciated.
>>
>> Please let me know if you have any thoughts or comments on this plan.
>>
>> [1]
>>
>> https://issues.apache.org/jira/browse/YARN-10347?jql=project%20in%20(YARN%2C%20HDFS%2C%20HADOOP%2C%20MAPREDUCE)%20AND%20status%20%3D%20Resolved%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20fixVersion%20%3D%203.2.2
>> [2]
>>
>> https://issues.apache.org/jira/browse/YARN-10345?jql=project%20in%20(YARN%2C%20HDFS%2C%20HADOOP%2C%20MAPREDUCE)%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22Patch%20Available%22)%20AND%20affectedVersion%20%3D%203.2.2
>>
>> Thanks,
>> He Xiaoqiao
>>
>>
>> On Wed, Sep 2, 2020 at 7:27 AM Wei-Chiu Chuang <weic...@apache.org>
>> wrote:
>>
>> > Hi folks,
>> >
>> > I was reminded by Xiaoqiao that Hadoop 3.2.1 was made almost a year ago
>> > (released on September 22, 2019) and we're overdue for a follow-up.
>> >
>> > @Rohith Sharma K S <rohithsharm...@apache.org>  you were the RM for
>> > Hadoop 3.2.1. Are we planning to make the 3.2.2 releases soon? Xiaoqiao
>> > wants to help with the release.
>> >
>> > Thanks,
>> > Weichiu
>> >
>>
>

Reply via email to