[jira] [Created] (ZOOKEEPER-3659) make the WatchManagerFactory log more readable

maoling created ZOOKEEPER-3659: -- Summary: make the WatchManagerFactory log more readable Key: ZOOKEEPER-3659 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3659 Project: ZooKeeper Issue Ty

ZooKeeper_branch34_jdk7 - Build # 2544 - Failure

See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/2544/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 47.04 KB...] [junit] Running org.apache.zookeep

Re: Messy releasenotes.md file on master and on website

Why not move to something managed/hosted by JIRA or perhaps Github? Patrick On Fri, Dec 20, 2019 at 2:20 AM Norbert Kalmar wrote: > +1 on option A. > But! > I think we should have a page containing all the changes in all supported > line. So like option C. > > Why? - I agree a specific release

Jenkins build is back to stable : PreCommit-ZOOKEEPER-github-pr-build-maven #1763

See

ZooKeeper_branch35_jdk8 - Build # 1644 - Still Failing

See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/1644/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 232.98 KB...] [exec] Log Message Received: [20

ZooKeeper_branch34_openjdk8 - Build # 545 - Still Failing

See https://builds.apache.org/job/ZooKeeper_branch34_openjdk8/545/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 48.09 KB...] [junit] Running org.apache.zook

Re: Messy releasenotes.md file on master and on website

+1 on option A. But! I think we should have a page containing all the changes in all supported line. So like option C. Why? - I agree a specific release should only contain changes to that version. If someone wants to see the changes that went into various releases, he/she should check the website

Jenkins build is still unstable: PreCommit-ZOOKEEPER-github-pr-build-maven #1762

See

[jira] [Created] (ZOOKEEPER-3658) Potential data inconsistency due to txns gap in committedLog when ZkDB not fully shutdown

Fangmin Lv created ZOOKEEPER-3658: - Summary: Potential data inconsistency due to txns gap in committedLog when ZkDB not fully shutdown Key: ZOOKEEPER-3658 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3658