Here are the meeting minutes:
https://cwiki.apache.org/confluence/display/BOOKKEEPER/2017-07-27+Meeting+Notes

- Sijie

On Thu, Jul 27, 2017 at 2:31 AM, Enrico Olivelli <eolive...@gmail.com>
wrote:

> I am sorry, I cannot attend.
>
> My notes:
> - switch from 4.4 to 4.5, look for differences, find performances
> regressions/improvements, check for API compatibility (see various
> issues/emails from me)
> - release plan and estimate for 4.5, I hope we could have a release within
> the start of September (vacations are coming for everyone I think....)
> - remaining parts from Twitter, Yahoo, Salesforce ?
> - ok for website, great work! Once pushed I would like to try git pub/sub
> - ok for slack channel, I don't know how this will change the interactions
> in the group, I would like that everyone could see the discussions, and the
> mailing list + github are very good, Slack will be more immediate ?
> - github issuetracker......we are on the good way!!
> - checkstyle....I hope we could move forward, not blocker for 4.5 for me
> - code coverage....I will go on, not blocker for 4.5 for me
> - we pushed Jenkins Job Builder, I am going to convert all the jobs but
> this week I am very busy, I will do as soon as possibile, not blocker for
> 4.5
> - SSL, let's try to finalize the work
> - http endpoint is it blocker for 4.5 ?
> - status of DL subproject ? how this will change BookKeeper community ?
>
> Cheers
> -- Enrico
>
>
>
> 2017-07-26 3:54 GMT+02:00 Jia Zhai <zhaiji...@gmail.com>:
>
> > Hi all, :)
> > I would like to put a draft Agenda here
> > <https://cwiki.apache.org/confluence/display/BOOKKEEPER/
> > 2017-07-27+Meeting+Agenda>
> > for
> > 7/27's meeting, this is just limited from my point of view, Please feel
> > free to add anything you want to discuss in this meeting.
> >
> > *Agenda:*
> >
> >    - Status of 4.5 release
> >    - New BookKeeper Website
> >    - Slack channel
> >    - 4.5 Performance regression?
> >    - Status of Bookkeeper Docker image
> >    - Other issues and PRs
> >
> > Thanks.
> >
>

Reply via email to