Junping, If we are looking at a month, I’d not rebranch branch-2.8.2 right now given how these things go. We can just continue to commit on branch-2.8 for now.
I also think we should just follow up with ASF INFRA and clean up the branches - Delete branch-2.8.2 so that we can recreate it afresh a little later. - branch-2.8.1 is also stale and it should be deleted. branch-2.8.1-private should be renamed to branch-2.8.1 Thanks +Vinod > On Jul 21, 2017, at 11:23 AM, Junping Du <j...@hortonworks.com> wrote: > > Thanks for suggestions, Jason and Kihwal! > +1 on releasing 2.8.2 on latest branch-2.8 too. Practically, if branch-2.8.2 > cannot be abandoned/replaced (suspect all branches are read-only now), I will > manually merge all commits that not landed on 2.8.2 yet. > > Thanks, > > Junping > ________________________________________ > From: Jason Lowe <jl...@yahoo-inc.com.INVALID> > Sent: Friday, July 21, 2017 8:17 AM > To: Kihwal Lee; Junping Du; common-...@hadoop.apache.org; > hdfs-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org; > yarn-...@hadoop.apache.org > Subject: Re: Apache Hadoop 2.8.2 Release Plan > > +1 to base the 2.8.2 release off of the more recent activity on branch-2.8. > Because branch-2.8.2 was cut so long ago it is missing a lot of fixes that > are in branch-2.8. There also are a lot of JIRAs that claim they are fixed > in 2.8.2 but are not in branch-2.8.2. Having the 2.8.2 release be based on > recent activity in branch-2.8 would solve both of these issues, and we'd only > need to move the handful of JIRAs that have marked themselves correctly as > fixed in 2.8.3 to be fixed in 2.8.2. > > Jason > > > On Friday, July 21, 2017 10:01 AM, Kihwal Lee > <kih...@yahoo-inc.com.INVALID> wrote: > > > Thanks for driving the next 2.8 release, Junping. While I was committing a > blocker for 2.7.4, I noticed some of the jiras are back-ported to 2.7, but > missing in branch-2.8.2. Perhaps it is safer and easier to simply rebranch > 2.8.2. > Thanks,Kihwal > > On Thursday, July 20, 2017, 3:32:16 PM CDT, Junping Du <j...@hortonworks.com> > wrote: > > Hi all, > Per Vinod's previous email, we just announce Apache Hadoop 2.8.1 get > released today which is a special security release. Now, we should work > towards 2.8.2 release which aim for production deployment. The focus > obviously is to fix blocker/critical issues [2], bug-fixes and *no* features > / improvements. We currently have 13 blocker/critical issues, and 10 of them > are Patch Available. > > I plan to cut an RC in a month - target for releasing before end of Aug., to > give enough time for outstanding blocker / critical issues. Will start moving > out any tickets that are not blockers and/or won't fit the timeline. For > progress of releasing effort, please refer our release wiki [2]. > > Please share thoughts if you have any. Thanks! > > Thanks, > > Junping > > [1] 2.8.2 release Blockers/Criticals: https://s.apache.org/JM5x > [2] 2.8 Release wiki: > https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release > > ________________________________________ > From: Vinod Kumar Vavilapalli <vino...@apache.org> > Sent: Thursday, July 20, 2017 1:05 PM > To: gene...@hadoop.apache.org > Subject: [ANNOUNCE] Apache Hadoop 2.8.1 is released > > Hi all, > > The Apache Hadoop PMC has released version 2.8.1. You can get it from this > page: http://hadoop.apache.org/releases.html#Download > This is a security release in the 2.8.0 release line. It consists of 2.8.0 > plus security fixes. Users on 2.8.0 are encouraged to upgrade to 2.8.1. > > Please note that 2.8.x release line continues to be not yet ready for > production use. Critical issues are being ironed out via testing and > downstream adoption. Production users should wait for a subsequent release in > the 2.8.x line. > > Thanks > +Vinod > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
