Personally I am waiting for BP-38 implementation to be committed.
https://github.com/apache/bookkeeper/pull/2314
(I just saw that Jia gave its feedback yesterday....so I am going to commit
that work)
We also have a few pending requests that need a second binding +1
It would be a pity to let them uncommitted given our pace of releases.
We should cut releases much more often
I think it is time to call for a volounter as release manager __
Enrico
Il giorno 27/05/20, 07:46 "Alessandro Luccaroni - Diennea"
<alessandro.luccar...@diennea.com> ha scritto:
Any news regarding release 4.10.1?
Thanks,
Alessandro
> -----Messaggio originale-----
> Da: Enrico Olivelli <eolive...@gmail.com>
> Inviato: lunedì 20 aprile 2020 09:33
> A: Bookkeeper-Dev <dev@bookkeeper.apache.org>
> Oggetto: Re: Release 4.11.0 and 4.10.0 "stable"
>
> Il giorno lun 20 apr 2020 alle ore 09:20 Anup Ghatage <ghat...@gmail.com>
> ha scritto:
>
> > We are about 60% of the way done for all pending work for 4.11.
> > So I agree with Sijie and give a +1 for 4.10.1
> >
>
> Sure
> +1 for 4.10.1
>
>
> Enrico
>
>
> >
> > Regards,
> > Anup
> >
> >
> > On Mon, Apr 20, 2020 at 12:18 AM Sijie Guo <guosi...@gmail.com> wrote:
> >
> > > I think we can make 4.10.1 first?
> > >
> > > - Sijie
> > >
> > > On Sun, Apr 19, 2020 at 11:05 PM Enrico Olivelli
> > > <eolive...@gmail.com>
> > > wrote:
> > >
> > > > Alessandro,
> > > > Thanks for pointing this out.
> > > >
> > > > From my point of view these items are to be checked:
> > > > - We have problems on Integration Tests (on GitHub Actions,
> > > >
> > > >
> > >
> >
> https://github.com/apache/bookkeeper/pull/2315/checks?check_run_id=60
> 0
> > 090302
> > > > ,
> > > > but I can reproduce the issue locally)
> > > > - we have a few PR pending
> > > > https://github.com/apache/bookkeeper/pulls
> > > some
> > > > of them are trivial but very useful new features or bug fixes
> > > > - we have this blocker issue from Ivan
> > > > https://github.com/apache/bookkeeper/pull/2303 that is related to
> > > > a
> > > patch
> > > > from Rajan already committed to master, we must reach consensus
> > > > here
> > > >
> > > > I hope that we can address all of this topic soon, then we can cut
> > 4.11.
> > > >
> > > > +1 about making 4.10 marked as stable as soon as we release 4.11
> > > >
> > > > Enrico
> > > >
> > > >
> > > > Il giorno lun 20 apr 2020 alle ore 07:22 Alessandro Luccaroni -
> > > > Diennea <alessandro.luccar...@diennea.com.invalid> ha scritto:
> > > >
> > > > > Hi BookKeepers,
> > > > > today is theoretically code freeze day for 4.11, see
> > > > > https://bookkeeper.apache.org/community/releases/
> > > > >
> > > > > Also, in the last 4 month we have released no minor release for
> > > > > 4.10
> > > and
> > > > > 4.9 (and 4.9.2 is still referenced as the "stable" release).
> > > > >
> > > > > Are there any plan to proceed with a 4.11 release? Do we wait
> > > > > for
> > > 4.10.1
> > > > > to declare 4.10 stable or we simply have to cast a vote?
> > > > >
> > > > > Regards,
> > > > > Alessandro Luccaroni
> > > > > Platform Manager @ Diennea - MagNews
> > > > > Tel.: (+39) 0546 066100 Int. 924 - Mob.: (+39) 393 7273519 Viale
> > > > > G.Marconi 30/14 - 48018 Faenza (RA) - Italy
> > > > >
> > > > >
> > > > > ________________________________
> > > > >
> > > > > CONFIDENTIALITY & PRIVACY NOTICE This e-mail (including any
> > > > > attachments) is strictly confidential and
> > > may
> > > > > also contain privileged information. If you are not the intended
> > > > recipient
> > > > > you are not authorised to read, print, save, process or disclose
> > > > > this message. If you have received this message by mistake,
> > > > > please inform
> > > the
> > > > > sender immediately and destroy this e-mail, its attachments and
> > > > > any
> > > > copies.
> > > > > Any use, distribution, reproduction or disclosure by any person
> > > > > other
> > > > than
> > > > > the intended recipient is strictly prohibited and the person
> > > responsible
> > > > > may incur in penalties.
> > > > > The use of this e-mail is only for professional purposes; there
> > > > > is no guarantee that the correspondence towards this e-mail will
> > > > > be read
> > only
> > > > by
> > > > > the recipient, because, under certain circumstances, there may
> > > > > be a
> > > need
> > > > to
> > > > > access this email by third subjects belonging to the Company.
> > > > >
> > > >
> > >
> >
> >
> > --
> > Anup Ghatage
> > www.ghatage.com
> >
________________________________
CONFIDENTIALITY & PRIVACY NOTICE
This e-mail (including any attachments) is strictly confidential and may
also contain privileged information. If you are not the intended recipient you
are not authorised to read, print, save, process or disclose this message. If
you have received this message by mistake, please inform the sender immediately
and destroy this e-mail, its attachments and any copies. Any use, distribution,
reproduction or disclosure by any person other than the intended recipient is
strictly prohibited and the person responsible may incur in penalties.
The use of this e-mail is only for professional purposes; there is no
guarantee that the correspondence towards this e-mail will be read only by the
recipient, because, under certain circumstances, there may be a need to access
this email by third subjects belonging to the Company.
________________________________
CONFIDENTIALITY & PRIVACY NOTICE
This e-mail (including any attachments) is strictly confidential and may also
contain privileged information. If you are not the intended recipient you are
not authorised to read, print, save, process or disclose this message. If you
have received this message by mistake, please inform the sender immediately and
destroy this e-mail, its attachments and any copies. Any use, distribution,
reproduction or disclosure by any person other than the intended recipient is
strictly prohibited and the person responsible may incur in penalties.
The use of this e-mail is only for professional purposes; there is no guarantee
that the correspondence towards this e-mail will be read only by the recipient,
because, under certain circumstances, there may be a need to access this email
by third subjects belonging to the Company.
