You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Sijie Guo <gu...@gmail.com> on 2019/11/20 02:25:00 UTC
[DISCUSS] Release 2.5.0
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
Re: [DISCUSS] Release 2.5.0
Posted by Sijie Guo <gu...@gmail.com>.
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 possible.
If you have any issues that you want to include in 2.5.0, please let me
know.
Thanks,
Sijie
On Wed, Nov 20, 2019 at 7:25 AM Sijie Guo <gu...@gmail.com> wrote:
> 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_...@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 <
>> mmerli@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
>> <mm...@apache.org>
>>
>> On Tue, Nov 19, 2019 at 6:25 PM Sijie Guo <gu...@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
>>
>
>
Re: [DISCUSS] Release 2.5.0
Posted by Sijie Guo <gu...@gmail.com>.
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_...@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 <
> mmerli@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
> <mm...@apache.org>
>
> On Tue, Nov 19, 2019 at 6:25 PM Sijie Guo <gu...@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
>
Re: [DISCUSS] Release 2.5.0
Posted by Chris Bartholomew <c_...@yahoo.com.INVALID>.
+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 <mm...@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
<mm...@apache.org>
On Tue, Nov 19, 2019 at 6:25 PM Sijie Guo <gu...@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
Re: [DISCUSS] Release 2.5.0
Posted by Matteo Merli <mm...@apache.org>.
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
<mm...@apache.org>
On Tue, Nov 19, 2019 at 6:25 PM Sijie Guo <gu...@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