On Mon, Jul 31, 2017 at 11:43 PM, Enrico Olivelli <eolive...@gmail.com> wrote:
> Great! > > some questions: > - TLS support ? will this be in ? > Yes. TLS will be in. > - There are a lot of flaky or constantly failing tests, shall we fix all of > them before preparing switching the master to 4.6 ? > Yes. We need to fix them. However cutting a 4.5 branch doesn't need to be blocked on it. If we cut 4.5, any fixes going forward has to be cherry-picked to 4.5 branch. Also, if the tests are only flaky on CI and passed most of time locally, I'd prefer not mark them as blockers. > > I hope that most of us are testing current 4.5 snapshots against their > applications in order to find regression > I we switch the master to 4.6 I can take care of continuing to push > manually the 4.5 snapshots > I don't know if we need to do that, because we are anyway in 4.5 release procedure. > > -- Enrico > > > 2017-08-01 8:40 GMT+02:00 Sijie Guo <guosi...@gmail.com>: > > > We've tried to clean up most of the issues marked for 4.5.0. I'd like to > > call a code freeze for 4.5.0. So no more issues/jiras should be marked in > > 4.5.0, unless it is really needed (e.g. bug fixes). > > > > Any new features should be marked as 4.6.0. I will work with JV to > prepare > > the 4.5 branch for release. > > > > If I miss anything critical that needs to be in 4.5.0, please point them > > out. > > > > Thanks, > > > > Sijie > > >
