No impact on 2.4.2. 2.4.x releases are bug fix releases for branch-2.4.
Thanks, Sijie On Wed, Nov 20, 2019 at 6:17 AM Chris Bartholomew <c_bartholo...@yahoo.com.invalid> wrote: > +1 to putting the features that are ready in 2.5 and moving the rest to > 2.6. The smaller the release, the smaller the regression risk. > Does this have any impact on 2.4.2? > Cheers,Chris > On Wednesday, November 20, 2019, 01:13:19 AM EST, Matteo Merli < > mme...@apache.org> wrote: > > SGTM, there are several things in flight (I for one would have liked > to get to bottom of meta-store refactoring in time for 2.5), though > there are already a lot of new features and improvements in current > master. > > -- > Matteo Merli > <mme...@apache.org> > > On Tue, Nov 19, 2019 at 6:25 PM Sijie Guo <guosi...@gmail.com> wrote: > > > > Hi all, > > > > It has been 5 months since our last major release 2.4.0 (was released on > > 06/30). There are already a lot of new features added to 2.5.0. I am > > starting the discussion of releasing 2.5.0 for a few reasons: > > > > 1) Make those features contributed to 2.5.0 available to Pulsar users as > > early as possible. > > 2) Follow the time based release plan (as proposed in PIP-47). > > > > For those features we can't complete soon, we can move them to 2.6.0. For > > example, transaction support. > > > > Let me know your thoughts. If there is no huge concerns, I volunteer to > be > > the release manager for 2.5.0 and shall be able to start the release > > process of 2.5.0 next week. > > > > Thanks, > > Sijie >
