Hi Rohith Thank you for initiating this
Few critical/blocker jira's we could consider YARN-9714 YARN-9642 YARN-9640 Regards Bibin -----Original Message----- From: Rohith Sharma K S [mailto:[email protected]] Sent: 21 August 2019 11:42 To: Wei-Chiu Chuang <[email protected]> Cc: Hdfs-dev <[email protected]>; yarn-dev <[email protected]>; mapreduce-dev <[email protected]>; Hadoop Common <[email protected]> Subject: Re: [DISCUSS] Hadoop-3.2.1 release proposal On Tue, 20 Aug 2019 at 22:28, Wei-Chiu Chuang <[email protected]> wrote: > Hi Rohith, > Thanks for initiating this. > I want to bring up one blocker issue: HDFS-13596 > <https://issues.apache.org/jira/browse/HDFS-13596> (NN restart fails > after RollingUpgrade from 2.x to 3.x) > > This should be a blocker for all active Hadoop 3.x releases: 3.3.0, > 3.2.1, 3.1.3. Hopefully we can get this fixed within this week. > Additionally, HDFS-14396 > <https://issues.apache.org/jira/browse/HDFS-14396> (Failed to load > image from FSImageFile when downgrade from 3.x to 2.x).Probably not a > blocker but nice to have. > >>>> Please set target version so that I don't miss in blockers/critical list for 3.2.1 https://s.apache.org/7yjh5. > > On Tue, Aug 20, 2019 at 3:22 AM Rohith Sharma K S < > [email protected]> wrote: > >> Hello folks, >> >> It's been more than six month Hadoop-3.2.0 is released i.e 16th Jan,2019. >> We have several important fixes landed in branch-3.2 (around 48 >> blockers/critical https://s.apache.org/ozd6o). >> >> I am planning to do a maintenance release of 3.2.1 in next few weeks >> i.e around 1st week of September. >> >> So far I don't see any blockers/critical in 3.2.1. I see few pending >> issues on 3.2.1 are https://s.apache.org/ni6v7. >> >> *Proposal*: >> Code Freezing Date: 30th August 2019 Release Date : 7th Sept 2019 >> >> Please let me know if you have any thoughts or comments on this plan. >> >> Thanks & Regards >> Rohith Sharma K S >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
