Hi all,
I have moved some of the issues that are not able to complete soon to 2.6.0.
There are still ~27 issues open. Hopefully we can get them merged this
week. https://github.com/apache/pulsar/milestone/22
If you have pending issues in 2.5.0 milestone, please help complete those
issues when po
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
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
+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
wrote:
SGTM, there are several things
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
On Tue, Nov 19, 2019 at 6:25 PM Sijie Guo wrote:
>
> Hi all,
>
> I
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 pos
