Re: Deprecate legacy API ? Which steps ?
+1 Best Regards. Jia Zhai Beijing, China Mobile: +86 15810491983 On Thu, Nov 21, 2019 at 6:29 AM Sijie Guo wrote: > +1 for deprecating the legacy API. > > Sijie > > On Wed, Nov 20, 2019 at 3:23 AM Enrico Olivelli > wrote: > > > Hi, > > I think it is time to work in the direction of deprecating the "old" > client > > API in favour of the new client API. > > > > Blockers: > > 1) Convert the documentation on the website to use only the new API > > 2) Let users of the new API use the 'Explicit LAC" feature > > > > > > for 2) I had sent in January a Pull Request > > https://github.com/apache/bookkeeper/pull/1901 > > > > I agreed with Sijie that we should think more about the proposal and my > > patch was not the best we could do. As it was not a showstopper for me I > > stopped the work. > > > > Thoughts ? > > > > Enrico > > >
Re: Bookkeeper stickers?
+1 Best Regards. Jia Zhai Beijing, China Mobile: +86 15810491983 On Fri, Nov 15, 2019 at 12:47 AM Venkateswara Rao Jujjuri wrote: > +1 > > On Thu, Nov 14, 2019 at 8:00 AM Anup Ghatage wrote: > > > That would be awesome! > > What can we do for those of us who can't attend the events but would > still > > like the stickers? > > > > Regards, > > Anup > > > > On Thu, Nov 14, 2019, 5:06 AM Enrico Olivelli > wrote: > > > > > Hi, > > > > > > We do not have Apache Bookkeeper stickers! > > > > > > I was at ApacheCon Europe and there were stickers for Zookeeper, > Pulsar, > > > Maven... > > > Nothing for Bookkeeper > > > > > > https://photos.apachecon.com/?/category/1 > > > > > > Shall we order new stickers for new Apache events? > > > > > > > > > Enrico > > > > > > > > -- > Jvrao > --- > First they ignore you, then they laugh at you, then they fight you, then > you win. - Mahatma Gandhi >
Re: [ANNOUNCE] Apache BookKeeper 4.10.0 released
👍 Best Regards. Jia Zhai Beijing, China Mobile: +86 15810491983 On Fri, Nov 15, 2019 at 3:14 AM Enrico Olivelli wrote: > The Apache BookKeeper team is proud to announce Apache BookKeeper version > 4.10.0. > > Apache BookKeeper is a scalable, fault-tolerant, and low-latency storage > service optimized for > real-time workloads. It has been used for a fundamental service to build > reliable services. > It is also the log segment store for Apache DistributedLog and the message > store for Apache Pulsar. > > This is the 20th release of the Apache BookKeeper. > > News and noteworthy: > - Add new bkctl shell tool > - Cluster Metadata Checker > - Journal should respect to flushWhenQueueEmpty setting > - Allow to override default SASL service name ‘bookkeeper’ > - Make default Bookie scripts work on JDK11+ > > For BookKeeper release details and downloads, visit: > > http://bookkeeper.apache.org/releases/ > > BookKeeper 4.10.0 Release Notes are at: > > http://bookkeeper.apache.org/docs/4.10.0/overview/releaseNotes/ > > We would like to thank the contributors that made the release possible. > > Regards, > > The BookKeeper Team >
Re: Deprecate legacy API ? Which steps ?
+1 for deprecating the legacy API. Sijie On Wed, Nov 20, 2019 at 3:23 AM Enrico Olivelli wrote: > Hi, > I think it is time to work in the direction of deprecating the "old" client > API in favour of the new client API. > > Blockers: > 1) Convert the documentation on the website to use only the new API > 2) Let users of the new API use the 'Explicit LAC" feature > > > for 2) I had sent in January a Pull Request > https://github.com/apache/bookkeeper/pull/1901 > > I agreed with Sijie that we should think more about the proposal and my > patch was not the best we could do. As it was not a showstopper for me I > stopped the work. > > Thoughts ? > > Enrico >
Website update after 4.10, Time Based Release plan and EOL
Hi BookKeepers, after the 4.10 release I see that the https://bookkeeper.apache.org/community/releases/ page needs some care. We are still listing 4.10 as the next feature release and we have skipped 3 release windows. I can see on Github that since the early 2019 the rate of contribution have slowed down a bit, so I think we should relax the Time Based Release Plan (new release every 6 month?). Apart from that, do we have an official EOL Policy for BookKeeper? On the website I see that we list all the version of BK back to v4.0.0 (2011) Many of these older version had very little usage, but since we are starting to see many project using BK downstream maybe we should clarify the full lifecycle of BK 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.
Deprecate legacy API ? Which steps ?
Hi, I think it is time to work in the direction of deprecating the "old" client API in favour of the new client API. Blockers: 1) Convert the documentation on the website to use only the new API 2) Let users of the new API use the 'Explicit LAC" feature for 2) I had sent in January a Pull Request https://github.com/apache/bookkeeper/pull/1901 I agreed with Sijie that we should think more about the proposal and my patch was not the best we could do. As it was not a showstopper for me I stopped the work. Thoughts ? Enrico
