Sounds like branch-2.8 was cut off prematurely. What is the point of forking off if the release is not imminent. We don't want this thing branching like a banyan again, with each commit going into 5 branches.
I think it would be easier to retire branch-2.8 for now, and reset it to branch-2.9 when you are ready to release, probably early next year. Unless of course you plan a 2.8 release by year end. Thanks, --Konst On Wed, Dec 16, 2015 at 6:52 PM, Vinod Kumar Vavilapalli <vino...@apache.org > wrote: > Not entirely sure we have enough info to warrant a hard-reset. Yet. > > Do we know how many of these are new features / improvement that we > shouldn’t put any more into 2.8.0 and how many are bugs that we need to? If > you don’t have time, I’ll look at it right after getting out 2.7.2 RC1. > > Thanks > +Vinod > > > On Dec 16, 2015, at 5:38 PM, Wangda Tan <wheele...@gmail.com> wrote: > > > > Hi folks, > > > > I found there're lots of commits are in branch-2 only. > > Ran "git log branch-2.8..branch-2". > > > > There're 35 commits for YARN, 41 commits for HDFS and 12 commits for > > COMMON. Only several of them are placed in 2.9.0 section in CHANGES.txt. > > > > I think we can either hard reset branch-2.8 to branch-2 and make > necessary > > changes such as revert 2.9.0-only patches or backport them one by one. > Any > > suggestions? > > > > Thanks, > > Wangda > >
