Having one standard time is good. But there needs to be participation too,
otherwise it won't be successful.
So lets find a good time that everyone can join. Other proposal is to setup
two meetings in a month, one is convenient for US
and other is convenient for Asia/Europe. Personally I am fine to
I think it is very difficult to find a good time slot for US, Europe and
Asia.
I would propose followings:
- keep the regular community meetings at 8AM PST and make sure all meeting
notes are updated and shared via mailing lists. Release manager should
drive the community meeting.
- additionally,
On Mon, Feb 11, 2019 at 6:09 AM Venkateswara Rao Jujjuri
wrote:
> Thanks for bringing this up. To start with, can we put all forms on LAC in
> a doc? i.e we have more than one way to read and write LAC.
> 1. What are the ways to send LAC to Bookies?
> 2. What are the ways bookies store the LAC?
>
FYI. I have submitted the board report.
Thanks Jia for drafting the report and all the reviewers reviewing the
report.
Great community work!
- Sijie
On Fri, Feb 8, 2019 at 8:13 AM Sijie Guo wrote:
> Good job, Jia. +1
>
> On Thu, Feb 7, 2019 at 4:11 PM Jia Zhai wrote:
>
>> Hi all,
>>
>> Here
I have also updated the release schedule :
http://bookkeeper.apache.org/community/releases/
On Sun, Feb 3, 2019 at 8:33 PM Enrico Olivelli wrote:
> New items:
> - make our binary packages work with jdk11
> - consider moving docker images to jdk11
>
> Enrico
>
> Il giorno sab 2 feb 2019, 01:08
Thanks for bringing this up. To start with, can we put all forms on LAC in
a doc? i.e we have more than one way to read and write LAC.
1. What are the ways to send LAC to Bookies?
2. What are the ways bookies store the LAC?
3. What are the ways client can learn about LAC
and the interfaces and conf
Hi Bookkeepers,
I am trying to draw the best roadmap with the goal of consolidating
ExplicitLAC feature.
Currently I have two big topics:
- on the reader side I would like enable new API users to leverage
ExplicitLAC, transparently (no new configuration, now readflags, no
explicit API calls)
- on t
