It is better to cut 4.8 release branch soon

[Enrico Olivelli <eo...@gmail.com>]

As I told at the meeting, it seems to me that the great work that is doing
Ivan is really greater than what we were expecting when we decided to defer
4.8.

We don't really are in a hurry for the binary metadata stuff, so we can
defer to 4.9.

I think it is safer to cut the 4.8 release branch soon, cherry pick ongoing
patches from JV and Andrey.

The issue found from Ivan about possible data loss should be fixed as well.

Opinions?

Enrico
-- 


-- Enrico Olivelli

Re: It is better to cut 4.8 release branch soon

[Enrico Olivelli <eo...@gmail.com>]

Master is at 4.9.0-SNAPSHOT

Please remember to cherry pick to 4.8 all the blockers, anyway I will keep
an eye.

I would be useful to have a minimal doc about Stream Storage Server as we
are releasing it, and as far as I understand it will be used in the
upcoming Pulsar release so we will have users but we have no doc at all.

We need to also document the change from Andrey about ref counting


Enrico



Il giorno ven 10 ago 2018 alle ore 11:44 Enrico Olivelli <
eolivelli@gmail.com> ha scritto:

> I am creating the release branch 4.8, so that Ivan will be able to move
> forward with "immutable" client side metadata stuff.
>
> Actually I will start the release process as soon as all the blocker
> issues are merged to master and cherry picked to 4.8
>
> Enrico
>
>
>
> Il giorno gio 9 ago 2018 alle ore 19:52 Sijie Guo <gu...@gmail.com> ha
> scritto:
>
>> +1 from me.
>>
>> On Thu, Aug 9, 2018 at 10:21 AM Enrico Olivelli <eo...@gmail.com>
>> wrote:
>>
>> > As I told at the meeting, it seems to me that the great work that is
>> doing
>> > Ivan is really greater than what we were expecting when we decided to
>> defer
>> > 4.8.
>> >
>> > We don't really are in a hurry for the binary metadata stuff, so we can
>> > defer to 4.9.
>> >
>> > I think it is safer to cut the 4.8 release branch soon, cherry pick
>> ongoing
>> > patches from JV and Andrey.
>> >
>>
>> What do you mean "cherry-pick" here? I thought we haven't cut branch-4.8,
>> no?
>>
>>
>> >
>> > The issue found from Ivan about possible data loss should be fixed as
>> well.
>> >
>> > Opinions?
>> >
>> > Enrico
>> > --
>> >
>> >
>> > -- Enrico Olivelli
>> >
>>
>

Re: It is better to cut 4.8 release branch soon

[Enrico Olivelli <eo...@gmail.com>]

I am creating the release branch 4.8, so that Ivan will be able to move
forward with "immutable" client side metadata stuff.

Actually I will start the release process as soon as all the blocker issues
are merged to master and cherry picked to 4.8

Enrico



Il giorno gio 9 ago 2018 alle ore 19:52 Sijie Guo <gu...@gmail.com> ha
scritto:

> +1 from me.
>
> On Thu, Aug 9, 2018 at 10:21 AM Enrico Olivelli <eo...@gmail.com>
> wrote:
>
> > As I told at the meeting, it seems to me that the great work that is
> doing
> > Ivan is really greater than what we were expecting when we decided to
> defer
> > 4.8.
> >
> > We don't really are in a hurry for the binary metadata stuff, so we can
> > defer to 4.9.
> >
> > I think it is safer to cut the 4.8 release branch soon, cherry pick
> ongoing
> > patches from JV and Andrey.
> >
>
> What do you mean "cherry-pick" here? I thought we haven't cut branch-4.8,
> no?
>
>
> >
> > The issue found from Ivan about possible data loss should be fixed as
> well.
> >
> > Opinions?
> >
> > Enrico
> > --
> >
> >
> > -- Enrico Olivelli
> >
>

Re: It is better to cut 4.8 release branch soon

[Sijie Guo <gu...@gmail.com>]

+1 from me.

On Thu, Aug 9, 2018 at 10:21 AM Enrico Olivelli <eo...@gmail.com> wrote:

> As I told at the meeting, it seems to me that the great work that is doing
> Ivan is really greater than what we were expecting when we decided to defer
> 4.8.
>
> We don't really are in a hurry for the binary metadata stuff, so we can
> defer to 4.9.
>
> I think it is safer to cut the 4.8 release branch soon, cherry pick ongoing
> patches from JV and Andrey.
>

What do you mean "cherry-pick" here? I thought we haven't cut branch-4.8,
no?


>
> The issue found from Ivan about possible data loss should be fixed as well.
>
> Opinions?
>
> Enrico
> --
>
>
> -- Enrico Olivelli
>