commit | 17baf76cb8ac61f1db0cfd36ce0b63787cbefaea | [log] [tgz] |
---|---|---|
author | Enrico Olivelli <eolivelli@gmail.com> | Thu Oct 22 01:47:11 2020 +0200 |
committer | GitHub <noreply@github.com> | Wed Oct 21 16:47:11 2020 -0700 |
tree | b27b8229cc5e9183945ce09f293d50b286689e62 | |
parent | ba42e6fe376d29b959eb002e76aa7b704ed47e4b [diff] |
Update website after 4.11.1 release: - fix BP page - fix versions list - fix download page and releases history - add script to publish the website manually - tagged as "stable" 4.10.0 - tagged as EOL every release < 4.9.2 - removed stale information about next releases (if we do not have a real plan it is better to not write stale information) - merge BK 4.11.1 release notes the procedure to publish the new website manually is: - git clone https://github.com/apache/bookkeeper - cd bookkeeper/site - docker/ci.sh - scripts/publish-website-manually.sh Reviewers: Anup Ghatage <ghatage@apache.org>, Nicolò Boschi <boschi1997@gmail.com> This closes #2448 from eolivelli/fix/update-website-after-4.11.1-release
Apache BookKeeper is a scalable, fault tolerant and low latency storage service optimized for append-only workloads.
It is suitable for being used in following scenarios:
You can also read Turning Ledgers into Logs to learn how to turn ledgers into continuous log streams. If you are looking for a high level log stream API, you can checkout DistributedLog.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.
Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.
Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.
Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.
We feel that a welcoming open community is important and welcome contributions.
See Developer Setup to get your local environment setup.
Take a look at our open issues: JIRA Issues Github Issues.
Review our coding style and follow our pull requests to learn about our conventions.
Make your changes according to our contribution guide.