Silly and off topic question: Why don't upgrade to 4.8.1 ? (I will send release announce today) Is it because it would be a major change and you are planning a minor release for Pulsar ?
Enrico -- Enrico Olivelli Software Development Manager @ Diennea - MagNews Tel.: (+39) 0546 066100 - Int. 125 Viale G.Marconi 30/14 - 48018 Faenza (RA) ________________________________________ Da: Sijie Guo <guosi...@gmail.com> Inviato: giovedì 29 novembre 2018 10:15 A: dev@bookkeeper.apache.org Oggetto: Re: Release 4.7.3 - db ledger storage flush bug - compaction scheduling bug - authentication with v2 protocol bug - don't cache bookie dns name resolution for the full list of bugs, it is here: https://github.com/apache/bookkeeper/issues?q=label%3Arelease%2F4.7.3+is%3Aclosed Any one who is using bk 4.7.2 will hit those issues above. From pulsar's perspective, Pulsar 2.2.1 needs 4.7.2. Thanks, Sijie On Thu, Nov 29, 2018 at 1:11 AM Ivan Kelly <iv...@apache.org> wrote: > What's the driving bugfix for cutting 4.7.3? > On Wed, Nov 21, 2018 at 11:54 PM Sijie Guo <guosi...@gmail.com> wrote: > > > > Hi all, > > > > I would like to cut a 4.7.3 release late this week. If you have any fixes > > to include in 4.7.3, please label those issues as 4.7.3, then I will make > > sure they are included. > > > > - Sijie > ________________________________ 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.
