Is it necessary to cut the branch so far ahead of the release? branch-3.0 is already a maintenance line for 3.0.x releases. Is there a known feature/improvement planned to go into branch-3.0 that is not desirable for the 3.0.1 release?
I have found in the past that branching so early leads to many useful fixes being unnecessarily postponed to future releases because committers forget to pick to the new, relatively long-lived patch branch. This becomes especially true if blockers end up dragging out the ultimate release date, which has historically been quite common. My preference would be to cut this branch as close to the RC as possible. Jason On Tue, Jan 9, 2018 at 1:17 PM, Lei Xu <l...@cloudera.com> wrote: > Hi, All > > We have released Apache Hadoop 3.0.0 in December [1]. To further > improve the quality of release, we plan to cut branch-3.0.1 branch > tomorrow for the preparation of Apache Hadoop 3.0.1 release. The focus > of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug fixes > [2]. No new features and improvement should be included. > > We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote for RC on Feb > 1st, targeting for Feb 9th release. > > Please feel free to share your insights. > > [1] https://www.mail-archive.com/general@hadoop.apache.org/msg07757.html > [2] https://issues.apache.org/jira/issues/?filter=12342842 > > Best, > -- > Lei (Eddy) Xu > Software Engineer, Cloudera > > --------------------------------------------------------------------- > To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org > >
