You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bookkeeper.apache.org by gi...@apache.org on 2019/02/28 15:57:50 UTC
[bookkeeper] branch asf-site updated: Updated site at revision
b67e8b2
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/bookkeeper.git
The following commit(s) were added to refs/heads/asf-site by this push:
new a8e3bb3 Updated site at revision b67e8b2
a8e3bb3 is described below
commit a8e3bb3abd5d9f862b934d4c7a0a81373def8108
Author: jenkins <bu...@apache.org>
AuthorDate: Thu Feb 28 15:57:47 2019 +0000
Updated site at revision b67e8b2
---
content/community/release_guide/index.html | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/content/community/release_guide/index.html b/content/community/release_guide/index.html
index 697f34f..4c3333d 100644
--- a/content/community/release_guide/index.html
+++ b/content/community/release_guide/index.html
@@ -517,7 +517,7 @@ if you are interested in learning more details.</p>
<p>Before cutting a release, you need to update the python client version in
<a href="https://github.com/apache/bookkeeper/blob/master/stream/clients/python/setup.py#L22">setup.py</a>
from <code class="highlighter-rouge">SNAPSHOT</code> version to a release version and get the change merge to master. For example,
-in release 4.10.0, you need to change the version from <code class="highlighter-rouge">4.10.0-SNAPSHOT</code> to <code class="highlighter-rouge">4.10.0</code>.</p>
+in release 4.10.0, you need to change the version from <code class="highlighter-rouge">4.10.0-alpha-0</code> to <code class="highlighter-rouge">4.10.0</code>.</p>
<h3 id="review-release-notes-in-github">Review Release Notes in Github</h3>
@@ -1022,10 +1022,11 @@ Then you have to create a PR and submit it for review.</p>
<p>If you are doing a major release, you need to update the python client version to next major development version in master
and next minor development version in the branch. For example, if you are doing 4.9.0 release, you need to bump the version
-in master to <code class="highlighter-rouge">4.10.0-SNAPSHOT</code>, and the version in <code class="highlighter-rouge">branch-4.9</code> to <code class="highlighter-rouge">4.9.1-SNAPSHOT</code>.</p>
+in master to <code class="highlighter-rouge">4.10.0-alpha-0</code> (NOTE: we are using <code class="highlighter-rouge">alpha-0</code> as <code class="highlighter-rouge">SNAPSHOT</code>, otherwise pypi doesn’t work), and the version in
+<code class="highlighter-rouge">branch-4.9</code> to <code class="highlighter-rouge">4.9.1-alpha-0</code>.</p>
<p>If you are only doing a minor release, you just need to update the version in release branch. For example, if you are doing
-4.9.1 release, you need to bump the version in <code class="highlighter-rouge">branch-4.9</code> to <code class="highlighter-rouge">4.9.2-SNAPSHOT</code>.</p>
+4.9.1 release, you need to bump the version in <code class="highlighter-rouge">branch-4.9</code> to <code class="highlighter-rouge">4.9.2-alpha-0</code>.</p>
<h3 id="mark-the-version-as-released-in-github">Mark the version as released in Github</h3>