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

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

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 >

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

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

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