Yes. 4.5.1 is the bugfix release, it is need basis. Any changes should go to master first, if it is a critical change, we can cherry-pick it to 4.5.1.
- Sijie On Sat, Aug 12, 2017 at 3:28 PM, Venkateswara Rao Jujjuri <jujj...@gmail.com > wrote: > On Fri, Aug 11, 2017 at 10:39 PM, Enrico Olivelli <eolive...@gmail.com> > wrote: > > > Il sab 12 ago 2017, 04:35 Jia Zhai <zhaiji...@gmail.com> ha scritto: > > > > > Hi, > > > I would like to have a a try on 4.6.0. > > > > > > On Sat, Aug 12, 2017 at 10:25 AM, Sijie Guo <guosi...@gmail.com> > wrote: > > > > > > > 4.5.0 is out. Although we haven't reached a conclusion whether we > want > > to > > > > adopt "Time Based Release Plan" yet, I would still like to start the > > > > discussion on the next releases. > > > > > > > > The next *feature* release will be 4.6.0 and we will probably have a > > bug > > > > fix 4.5.1 for branch 4.5. all the features will go to master and be > > > > included in 4.6.0; bug fixes will first go to master, if they impact > > > 4.5.0, > > > > those changes will be cherry-pick to branch-4.5 (on merging) and be > > > > included in 4.5.1. > > > > > > > > Besides that, there are a few things we need to discuss and plan > here: > > > > > > > > - what changes that we are planning to include in 4.6.0? If you > already > > > > have ideas, please bring them upfront. If you don't have anyone now, > > you > > > > can create issues later and mark them as `4.6.0` > > > > > > > I will create issues as soon as possible, but my (my company) areas of > > urgent work are: > > - java9 build, maybe non yes official support > > > > - relax durability, that is to not wait for synch on journal for some > > entries > > > > > > > > > > > > > [Jia] we have some changes that we'd like to get in. I will create > > issues > > > soon. > > > > > > > > > > - who will be the release managers to drive the next two releases? > one > > is > > > > for 4.6.0 feature release, the other one is 4.5.1 bug fix release. we > > > > should start a rotation between committers to drive the releases. Any > > > > volunteers for driving the releases? > > > > > > > > > > [Jia] I would like to have a try on 4.6.0. > > > > > > > I am available, for 4.6, 4.7 or even for 4.5.1 > > > > > > > > > > > > - how long that we should target for 4.6.0 and 4.5.1? If we adopted > > `Time > > > > Based Release Plan`, we will be targeting at 4.6.0 release in > November. > > > For > > > > bug fix release, it can be a shorter one, around one month. > > > > > > > You think that we will need soon some horfix? 4.4 lasted one year and we > > did not need any 4.4.1. Maybe now 4.5 will be more adopted? > > > > > This is good point. Usually if we have any customers that are purely based > on the community 4.5.0 release > then it warrants identifying what fixes need to be rolled back from master > (4.6). So it really depends on the > needs of 4.5.0 users, and the release of 4.5.1 should be need basis. Its ok > if we never need to do 4.5.0 and > come out 4.6.0, but we need to follow the rule that every new change should > go into master first, as suggested > by Sijie. I like time based release idea and lets pick a date . :) > > JV > > > > Enrico > > > > > > > > > [Jia] Sound good. > > > > > > > > > > Thoughts, Volunteers? > > > > > > > > - Sijie > > > > > > > > > -- > > > > > > -- Enrico Olivelli > > > > > > -- > Jvrao > --- > First they ignore you, then they laugh at you, then they fight you, then > you win. - Mahatma Gandhi >
