This is an automated email from the ASF dual-hosted git repository.
guangning pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new f9078b8 Updated Release process (markdown)
f9078b8 is described below
commit f9078b89e5a3039930ec11c5231697aa0225726e
Author: Guangning <[email protected]>
AuthorDate: Wed Jan 22 12:10:06 2020 +0800
Updated Release process (markdown)
---
Release-process.md | 36 ++++++++++++++++++------------------
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/Release-process.md b/Release-process.md
index e5c58aa..0a1143b 100644
--- a/Release-process.md
+++ b/Release-process.md
@@ -17,15 +17,15 @@ The steps for releasing are as follows:
6. Move master branch to next version
7. Write release notes
8. Run the vote
-10. Promote the release
-11. Publish Docker Images
-12. Publish Python
-13. Update swagger file
-14. Update release notes
-15. Update the site
-16. Announce the release
-17. Write a blog post for the release (optional)
-18. Remove old releases
+19. Promote the release
+10. Publish Docker Images
+11. Publish Python
+12. Update swagger file
+13. Update release notes
+14. Update the site
+15. Announce the release
+16. Write a blog post for the release (optional)
+17. Remove old releases
## Steps in detail
@@ -233,7 +233,7 @@ vote as well.
If the release is approved here, we can then proceed to next step.
-#### 10. Promote the release
+#### 9. Promote the release
Create the final git tag:
@@ -253,7 +253,7 @@ select the staging repository associated with the RC
candidate that was approved
will be like `orgapachepulsar-XYZ`. Select the repository and click on
"Release". Artifacts
will now be made available on Maven central.
-#### 11. Publish Docker Images
+#### 10. Publish Docker Images
- a) Run `cd $PULSAR_HOME/docker && ./build.sh` build docker images.
- b) Run `cd $PULSAR_HOME/docker && ./publish.sh` publish all images, once it
is done, check https://hub.docker.com/r/apachepulsar/pulsar/tags/ to make sure
the docker image is published.
@@ -261,7 +261,7 @@ will now be made available on Maven central.
> Note: ask Matteo or Sijie for adding you as a maintainer for publishing the
> docker images
-#### 12. Publish Python Clients
+#### 11. Publish Python Clients
> ##### NOTES:
>
@@ -316,7 +316,7 @@ Then you can run `twin upload` to upload those wheel files.
If you don't have enough spaces, you can build the python wheel file platform
by platform and remove the images under `~/.vagrant.d/boxes` between each run.
-#### 13. Update swagger file
+#### 12. Update swagger file
> the swagger file update always happen under `master` branch.
@@ -330,11 +330,11 @@ cp pulsar-broker/target/docs/*.json
site2/website/static/swagger/2.X.0
```
Send out a PR request for review.
-#### 14. Update release notes
+#### 13. Update release notes
Follow [this example](https://github.com/apache/pulsar/pull/2292) to add the
release notes there.
-#### 15. Update the site
+#### 14. Update the site
> the website update always happen under `master` branch.
@@ -377,7 +377,7 @@ git add versioned_docs/version-<release-version>
9. Publish the release on GitHub, copying the same release notes:
https://github.com/apache/pulsar/releases
-#### 16. Announce the release
+#### 15. Announce the release
Once the release artifacts are available in the Apache Mirrors and the website
is updated,
we need to announce the release.
@@ -409,13 +409,13 @@ Regards,
The Pulsar Team
```
-#### 17. Write a blog post for the release (optional)
+#### 16. Write a blog post for the release (optional)
It is encouraged to write a blog post to summarize the features introduced in
this release,
especially for feature releases.
You can follow the example [here](https://github.com/apache/pulsar/pull/2308)
-#### 18. Remove old releases
+#### 17. Remove old releases
Remove the old releases (if any). We only need the latest release there, older
releases are
available through the Apache archive:
