Thanks JV.
Comments are left in the google doc.
Let's continue the discussion on the google doc. Create the corresponding
BPs/issues for individual problems, so that we can move this stuff forward.
- Sijie
On Tue, Jan 16, 2018 at 12:33 PM, Venkateswara Rao Jujjuri <
jujj...@gmail.com> wrote:
>
Thank you Enrico!
- Sijie
On Wed, Jan 17, 2018 at 5:44 AM, Enrico Olivelli
wrote:
> This is the list of most useful patches submitted:
>
> Basic Implementation on the Journal of DEFERRED_SYNC write flags. We are
> only passing the flag down to the journal and expect to receive an ack only
> aft
This is the list of most useful patches submitted:
Basic Implementation on the Journal of DEFERRED_SYNC write flags. We are
only passing the flag down to the journal and expect to receive an ack only
after flushing data to disk
https://github.com/apache/bookkeeper/pull/889
Basic Implementation of
Il mer 17 gen 2018, 09:48 Ivan Kelly ha scritto:
> A PR and an issue are almost identical in github though. What is the
> advantage of having an issue, if all the discussion is on the PR?
>
The only problem is about creating release notes. Items are duplicated and
it is difficult to create a nic
A PR and an issue are almost identical in github though. What is the
advantage of having an issue, if all the discussion is on the PR?
On Wed, Jan 17, 2018 at 7:01 AM, Jia Zhai wrote:
> +1,
> From my view, it is better to "have an issue for each PR".
>
> On Wed, Jan 17, 2018 at 4:28 AM, Enrico Ol
