Re: BP-9 - Github issues for Issue Tracking

Thanks Jia. More comments added on Enrico's. There are unknowns related INFRA permissions. It might be making sense for you to reach out first and update what permissions work in the BP. So other people knows the INFRA situation. On Jun 11, 2017 4:38 AM, "Enrico Olivelli"

[GitHub] bookkeeper issue #181: BOOKKEEPER-1089: Ledger Recovery (part-4) - allow bat...

Github user sijie commented on the issue: https://github.com/apache/bookkeeper/pull/181 It is still blocked on #180. I already pinged on that pr. Do you mind letting me managing the merge on these patches, because they have sequence and dependencies? --- If your project is set up

Jenkins build is back to normal : bookkeeper-master #1781

See

Re: BP-9 - Github issues for Issue Tracking

Thank you Jia for starting the discussion. I think the labes/milestones can work as you described, but maybe we can consider to use composite labels like component/server or type/improvement. Good idea the fact to only mark blocker issues, it is a good starting point, simple but effective Good

[jira] [Commented] (BOOKKEEPER-1089) Ledger Recovery - allow batch reads in ledger recovery

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16045907#comment-16045907 ] ASF GitHub Bot commented on BOOKKEEPER-1089: Github user eolivelli commented on the

[GitHub] bookkeeper issue #181: BOOKKEEPER-1089: Ledger Recovery (part-4) - allow bat...

Github user eolivelli commented on the issue: https://github.com/apache/bookkeeper/pull/181 @sijie this patch has been reviewed and all previous commits have been merged, can you rebase ? --- If your project is set up for it, you can reply to this email and have your reply appear