Hi Sahil, We have done releases like 2.3 and 2.4 off branch-2 instead of master in past.
The idea is to keep master for all major features (e.g. removing support for MR) and keep 3.1 for only minor features plus bug fixes. Vineet > On May 22, 2018, at 1:11 PM, Sahil Takiar <[email protected]> wrote: > > Is there a reason we want to only release 3.x on branch-3? I don't think > this is what we did for the 2.1.0 and 2.2.0 releases. > > Given that most of the changes in Hive go into master, why would we want to > upgrade it to 4.0 given that we just released 3.0? > > On Wed, May 16, 2018 at 1:03 PM, Vineet Garg <[email protected]> wrote: > >> Hello, >> >> An update on release branches: >> >> I have created a new branch branch-3.0 off branch-3 which is being used to >> release Hive 3.0. branch-3 will continue to be used for 3.x releases. >> I am preparing branch-3 for 3.1 release and is now open for commits. >> Please ping me if you would like to get your commit to branch-3 keeping in >> mind that we should target only minor features and bug fixes in there. >> Master will continue to be used for major features in 4.0. >> >> >> Thanks, >> Vineet Garg >> > > > > -- > Sahil Takiar > Software Engineer > [email protected] | (510) 673-0309
