My thinking is to cut the branch in next couple of days and create RC for vote at the end of month. > We plan to cut branch-3.0.3 by the coming Wednesday (May 9th) and vote for RC on May 30th I much prefer to wait to cut the branch until just before the production of the release and the vote. With so many branches, we sometimes miss putting critical bug fixes in unreleased branches if the branch is cut too early.
Echoing Eric Payne, I think we should wait to cut the branch until we are actually creating the RC to vote on (i.e. on May 29 or 30 if the vote is to be on May 30). Eric On Wed, May 23, 2018 at 4:11 PM, Yongjun Zhang <yzh...@cloudera.com> wrote: > Hi, > > I have gardened the jiras for 3.0.3, and have the following open issues: > > https://issues.apache.org/jira/issues/?filter=12343970 > > Two of them are blockers, one of them (YARN-8346) has already got +1 for > patch, the other (YARN-8108) will take longer time to resolve and it seems > we can possibly push it to next release given 3.0.2 also has the issue. > > My thinking is to cut the branch in next couple of days and create RC for > vote at the end of month. > > Comments are welcome. > > Thanks, > > --Yongjun > > On Tue, May 8, 2018 at 11:40 AM, Vrushali C <vrushalic2...@gmail.com> > wrote: > > > +1 for including the YARN-7190 patch in 3.0.3 release. This is a fix that > > will enable HBase to use Hadoop 3.0.x in the production line. > > > > thanks > > Vrushali > > > > > > On Tue, May 8, 2018 at 10:24 AM, Yongjun Zhang <yzh...@cloudera.com> > > wrote: > > > >> Thanks Wei-Chiu and Haibo for the feedback! > >> > >> Good thing is that I have made the following note couple of days ago > when > >> I > >> looked the at branch diff, so we are on the same page: > >> > >> 496dc57 Revert "YARN-7190. Ensure only NM classpath in 2.x gets > TSv2 > >> related hbase jars, not the user classpath. Contributed by Varun > Saxena." > >> > >> *YARN-7190 is not in 3.0.2, I will include it in 3.0.3 per* the comment > >> below: > >> https://issues.apache.org/jira/browse/YARN-7190?focusedComme > >> ntId=16457649& > >> page=com.atlassian.jira.plugin.system.issuetabpanels > >> <https://issues.apache.org/jira/browse/YARN-7190? > focusedCommentId=16457649&page=com.atlassian.jira. > plugin.system.issuetabpanels> > >> : > >> comment-tabpanel#comment-16457649 > >> > >> > >> In addition, I will revert https://issues.apache.org/ > >> jira/browse/HADOOP-13055 from 3.0.3 since it's a feature. > >> > >> > >> Best, > >> > >> --Yongjun > >> > >> On Tue, May 8, 2018 at 8:57 AM, Haibo Chen <haiboc...@cloudera.com> > >> wrote: > >> > >> > +1 on adding YARN-7190 to Hadoop 3.0.x despite the fact that it is > >> > technically incompatible. > >> > It is critical enough to justify being an exception, IMO. > >> > > >> > Added Rohith and Vrushali > >> > > >> > On Tue, May 8, 2018 at 6:20 AM, Wei-Chiu Chuang <weic...@apache.org> > >> > wrote: > >> > > >> >> Thanks Yongjun for driving 3.0.3 release! > >> >> > >> >> IMHO, could we consider adding YARN-7190 > >> >> <https://issues.apache.org/jira/browse/YARN-7190> into the list? > >> >> I understand that it is listed as an incompatible change, however, > >> because > >> >> of this bug, HBase considers the entire Hadoop 3.0.x line not > >> production > >> >> ready. I feel there's not much point releasing any more 3.0.x > releases > >> if > >> >> downstream projects can't pick it up (after the fact that HBase is > one > >> of > >> >> the most important projects around Hadoop). > >> >> > >> >> On Mon, May 7, 2018 at 1:19 PM, Yongjun Zhang <yzh...@cloudera.com> > >> >> wrote: > >> >> > >> >> > Hi Eric, > >> >> > > >> >> > Thanks for the feedback, good point. I will try to clean up things, > >> then > >> >> > cut branch before the release production and vote. > >> >> > > >> >> > Best, > >> >> > > >> >> > --Yongjun > >> >> > > >> >> > On Mon, May 7, 2018 at 8:39 AM, Eric Payne < > eric.payne1...@yahoo.com > >> . > >> >> > invalid > >> >> > > wrote: > >> >> > > >> >> > > > We plan to cut branch-3.0.3 by the coming Wednesday (May 9th) > >> and > >> >> vote > >> >> > > for RC on May 30th > >> >> > > I much prefer to wait to cut the branch until just before the > >> >> production > >> >> > > of the release and the vote. With so many branches, we sometimes > >> miss > >> >> > > putting critical bug fixes in unreleased branches if the branch > is > >> cut > >> >> > too > >> >> > > early. > >> >> > > > >> >> > > My 2 cents... > >> >> > > Thanks, > >> >> > > -Eric Payne > >> >> > > > >> >> > > > >> >> > > > >> >> > > > >> >> > > > >> >> > > On Monday, May 7, 2018, 12:09:00 AM CDT, Yongjun Zhang < > >> >> > > yjzhan...@apache.org> wrote: > >> >> > > > >> >> > > > >> >> > > > >> >> > > > >> >> > > > >> >> > > Hi All, > >> >> > > > >> >> > > > > >> >> > > We have released Apache Hadoop 3.0.2 in April of this year [1]. > >> Since > >> >> > then, > >> >> > > there are quite some commits done to branch-3.0. To further > improve > >> >> the > >> >> > > quality of release, we plan to do 3.0.3 release now. The focus of > >> >> 3.0.3 > >> >> > > will be fixing blockers (3), critical bugs (17) and bug fixes > >> (~130), > >> >> see > >> >> > > [2]. > >> >> > > > >> >> > > Usually no new feature should be included for maintenance > >> releases, I > >> >> > > noticed we have https://issues.apache.org/ > jira/browse/HADOOP-13055 > >> in > >> >> > the > >> >> > > branch classified as new feature. I will talk with the developers > >> to > >> >> see > >> >> > if > >> >> > > we should include it in 3.0.3. > >> >> > > > >> >> > > I also noticed that there are more commits in the branch than can > >> be > >> >> > found > >> >> > > by query [2], also some commits committed to 3.0.3 do not have > >> their > >> >> jira > >> >> > > target release field filled in accordingly. I will go through > them > >> to > >> >> > > update the jira. > >> >> > > > >> >> > > > > >> >> > > We plan to cut branch-3.0.3 by the coming Wednesday (May 9th) and > >> vote > >> >> > for > >> >> > > RC on May 30th, targeting for Jun 8th release. > >> >> > > > >> >> > > > > >> >> > > Your insights are welcome. > >> >> > > > >> >> > > > > >> >> > > [1] https://www.mail-archive.com/general@hadoop.apache.org/msg07 > >> >> 790.html > >> >> > > > >> >> > > > [2] https://issues.apache.org/jira/issues/?filter=12343874 > See > >> >> Note > >> >> > > below > >> >> > > Note: seems I need some admin change so that I can make the > filter > >> in > >> >> [2] > >> >> > > public, I'm working on that. For now, you can use jquery > >> >> > > (project = hadoop OR project = "Hadoop HDFS" OR project = "Hadoop > >> >> YARN" > >> >> > OR > >> >> > > project = "Hadoop Map/Reduce") AND fixVersion in (3.0.3) ORDER BY > >> >> > priority > >> >> > > DESC > >> >> > > > >> >> > > Thanks and best regards, > >> >> > > > >> >> > > --Yongjun > >> >> > > > >> >> > > ------------------------------------------------------------ > >> --------- > >> >> > > To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hado > >> op.apache.org > >> >> > > For additional commands, e-mail: mapreduce-dev-h...@hadoop.apac > >> he.org > >> >> > > > >> >> > > > >> >> > > >> >> > >> >> > >> >> > >> >> -- > >> >> A very happy Hadoop contributor > >> >> > >> > > >> > > >> > > > > >
