Okay to me 4.8 is a big jump and it is taking quite lonng time Enrico
Il gio 16 ago 2018, 10:18 Sijie Guo <guosi...@gmail.com> ha scritto: > On Thu, Aug 16, 2018 at 12:48 AM Ivan Kelly <iv...@apache.org> wrote: > > > What changes are in 4.8.0 that was prevent users from moving directly to > > that? > > > > In theory, there aren't changes in 4.8.0 preventing users from moving > directly from 4.7.1 to 4.8.0. > > However in practice, moving from one feature release to another feature > release has higher risks, than upgrading with a bugfix release. > That's why we keep feature releases going on in master, while still having > bugfix releases for each feature release. > > > > > > > > Is anyone requesting 4.7.2? > > > > A bugfix release is for addressing issues found in a major/feature > release. If there are bug reported from 4.7.0 or 4.7.1, we should > have to provide a bugfix release for the users. > > We can't force users moving to a major release just for bug fixes, > especially if those users are running a production system. > So we need a bugfix release 4.7.2 for the users who have been using 4.7.0 > or 4.7.1. > > In a more concrete example, currently Pulsar 2.1.0 is using BK 4.7.1. There > have been multiple issues reported from Pulsar users using 4.7.1. > In order to address the problems facing by the users using BK 4.7.1, we > have to create this 4.7.2 release for fixing the bugs in 4.7.1. > > - Sijie > > > > > > > -Ivan > > > > On Thu, Aug 16, 2018 at 8:59 AM, Sijie Guo <guosi...@gmail.com> wrote: > > > Hi all, > > > > > > There are bunch of fixes cherry-picked into branch-4.7 and some are > > marked > > > for cherry-picking to branch-4.7. I think it is time to discuss > cutting a > > > bug fix release 4.7.2. Any thoughts? > > > > > > - Sijie > > > -- -- Enrico Olivelli
