This is an automated email from the ASF dual-hosted git repository.
zhaijia pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/bookkeeper.git
The following commit(s) were added to refs/heads/master by this push:
new f14be64 ISSUE #818: add api changes in release notes of 4.6.0
f14be64 is described below
commit f14be643e9fdc4db39323bc98e2735cfb169e75e
Author: Jia Zhai <[email protected]>
AuthorDate: Sat Dec 9 16:38:57 2017 +0800
ISSUE #818: add api changes in release notes of 4.6.0
Descriptions of the changes in this PR:
add changes of BookKeeper constructor and EnsemblePlacementPolicy in
release notes of 4.6.0
Master Issue: #818
Author: Jia Zhai <[email protected]>
Reviewers: Enrico Olivelli <[email protected]>, Sijie Guo
<[email protected]>
This closes #822 from jiazhai/issue-818, closes #818
---
site/docs/4.6.0/overview/releaseNotes.md | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/site/docs/4.6.0/overview/releaseNotes.md
b/site/docs/4.6.0/overview/releaseNotes.md
index 84cdd06..3bd0116 100644
--- a/site/docs/4.6.0/overview/releaseNotes.md
+++ b/site/docs/4.6.0/overview/releaseNotes.md
@@ -56,6 +56,11 @@ The main features in 4.6.0 cover are around following areas:
- Deployment BookKeeper on K8s.
- Provide yaml files to run BookKeeper on Kubernetes using both StatefulSets
and DaemonSet. See [Issue-337](https://github.com/apache/bookkeeper/issues/337)
and [Issue-681](https://github.com/apache/bookkeeper/issues/681)for more
details.
+## Existing API changes
+
+- BookKeeper constructor now throws BKException instead of KeeperException.
+- The signatures of `reorderReadSequence` and `reorderReadLACSequence` are
changed in EnsemblePlacementPolicy.
+
## Full list of changes
--
[https://github.com/apache/bookkeeper/milestone/2](https://github.com/apache/bookkeeper/milestone/2)
\ No newline at end of file
+-
[https://github.com/apache/bookkeeper/milestone/2?closed=1](https://github.com/apache/bookkeeper/milestone/2?closed=1)
\ No newline at end of file
--
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].
