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 f6b82b4 Updated Release process (markdown)
f6b82b4 is described below
commit f6b82b4262d237da360514d5401716abb236e4db
Author: Guangning <[email protected]>
AuthorDate: Wed Jan 22 12:03:25 2020 +0800
Updated Release process (markdown)
---
Release-process.md | 24 +++++++++++++++++++-----
1 file changed, 19 insertions(+), 5 deletions(-)
diff --git a/Release-process.md b/Release-process.md
index c99e715..3dd8722 100644
--- a/Release-process.md
+++ b/Release-process.md
@@ -314,11 +314,25 @@ 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 release notes
+#### 13. Update swagger file
+
+> the swagger file update always happen under `master` branch.
+
+```shell
+git checkout branch-2.5
+mvn -am -pl pulsar-broker install -DskipTests -Pswagger
+git checkout master
+git checkout -b fix/swagger-file
+mkdir -p site2/website/static/swagger/2.X.0
+cp pulsar-broker/target/docs/*.json site2/website/static/swagger/2.X.0
+```
+Send out a PR request for review.
+
+#### 14. Update release notes
Follow [this example](https://github.com/apache/pulsar/pull/2292) to add the
release notes there.
-#### 14. Update the site
+#### 15. Update the site
> the website update always happen under `master` branch.
@@ -361,7 +375,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
-#### 15. Announce the release
+#### 16. Announce the release
Once the release artifacts are available in the Apache Mirrors and the website
is updated,
we need to announce the release.
@@ -393,13 +407,13 @@ Regards,
The Pulsar Team
```
-16. Write a blog post for the release (optional)
+17. 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)
-17. Remove old releases
+18. Remove old releases
Remove the old releases (if any). We only need the latest release there, older
releases are
available through the Apache archive:
