Okay Enrico, go ahead please. Andor
On Tue, Dec 10, 2019 at 10:42 AM Norbert Kalmar <nkal...@cloudera.com.invalid> wrote: > +1 to create the 3.6 branch now. I don't expect a whole lot of patches that > needs to be added to 3.6 and master as well. Only the few remaining tickets > that is planned and occasional bugfixes. But, imho, better to push out a > 3.6.0 that no one will probably use because they'll just wait for a 3.6.1 > "stable" :) And as Enrico pointed out, branching speeds things up, as the > work for releasing can start with things like testing and stabilization. > > Regards, > Norbert > > On Mon, Dec 9, 2019 at 4:28 PM Enrico Olivelli <eolive...@gmail.com> > wrote: > > > Il giorno lun 9 dic 2019 alle ore 14:00 Andor Molnar <an...@apache.org> > ha > > scritto: > > > > > Thanks for driving this Enrico. > > > > > > a.) Version number: I think we discussed this already and agreed on > 3.7.0 > > > for now. As Enrico pointed out we can change it at any time anyway. > > > > > > b.) Why do you want to cut now instead of the point when we do the > first > > > release? To me it will just add one more branch when committing. What > are > > > the pros? > > > > > > > > > Because we are close to the release (hopefully). > > We have a few patches that the community (Andro, Fangmin....) wanted to > add > > on 3.6.0, all of the other patches can go to 3.6.0 > > > > Once we have a branch-3.6 we can focus on consolidation, manual > testing... > > I we continue to add patches we can't be sure the branch is very good > shape > > before the release > > > > I really would like to have the first RC before Christmas > > > > Enrico > > > > > > > > > > > > Andor > > > > > > > > > > > > > On 2019. Dec 9., at 13:37, Enrico Olivelli <eolive...@gmail.com> > > wrote: > > > > > > > > Tamas, > > > > > > > > Il lun 9 dic 2019, 13:33 Tamas Penzes <tam...@cloudera.com.invalid> > ha > > > > scritto: > > > > > > > >> Hi All, > > > >> > > > >> Just a question to the community, should we set the version number > to > > > >> 4.0.0-SNAPSHOT in the master branch? > > > >> > > > > > > > > We will use 4 when we decide to break compatibility in a very hard > way. > > > > > > > > Currently there is no plan, so I would go with 3.7.0. > > > > > > > > Btw We can change it at any time. > > > > Let's make one step at a time > > > > > > > > Thanks for bringing up the topic > > > > > > > > Enrico > > > > > > > > I think it's time to decide whether we want to do it or not. > > > >> > > > >> Regards, Tamaas > > > >> > > > >> On Mon, Dec 9, 2019 at 8:53 AM Enrico Olivelli <eolive...@gmail.com > > > > > >> wrote: > > > >> > > > >>> Hi folks, > > > >>> I think it is time to create branch-3.6 and bump master to > > > 3.7.0-SNAPSHOT > > > >>> > > > >>> This does not mean to release 3.6.0, we can still cherry pick > patches > > > >> from > > > >>> master brach. > > > >>> But it is time to start consolidating the branch and pick only > > > important > > > >>> changes > > > >>> > > > >>> If no one objects I will proceed with this step next weekend (14-15 > > > >>> December) > > > >>> > > > >>> Best regards > > > >>> > > > >>> Enrico > > > >>> > > > >> > > > > > > > > >
