This is an automated email from the ASF dual-hosted git repository.
massakam pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-client-node.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new 1641299 Updated Release process (markdown)
1641299 is described below
commit 1641299862ba7dd1deadb4324c0b1c09e61ac49c
Author: Masahiro Sakamoto <[email protected]>
AuthorDate: Thu Aug 29 14:07:27 2019 +0900
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 077bc63..a2c33a8 100644
--- a/Release-process.md
+++ b/Release-process.md
@@ -18,15 +18,15 @@ The steps for releasing are as follows:
#### 1. Create the release branch
-We are going to create a branch from `master` to `branch-0.X` where the tag
will be generated
+We are going to create a branch from `master` to `branch-1.X` where the tag
will be generated
and where new fixes will be applied as part of the maintenance for the release.
The branch needs only to be created when creating minor releases, and not for
patch releases.
-Eg: When creating `v0.1.0` release, will be creating the branch `branch-0.1`,
-but for `v0.1.1` we would keep using the old `branch-0.1`.
+Eg: When creating `v1.1.0` release, will be creating the branch `branch-1.1`,
+but for `v1.1.1` we would keep using the old `branch-1.1`.
-In these instructions, I'm referring to an fictitious release `0.X.0`.
+In these instructions, I'm referring to an fictitious release `1.X.0`.
Change the release version in the examples accordingly with the real version.
It is recommended to create a fresh clone of the repository to avoid any local
files to interfere
@@ -35,7 +35,7 @@ in the process:
```sh
$ git clone [email protected]:apache/pulsar-client-node.git
$ cd pulsar-client-node
-$ git checkout -b branch-0.X origin/master
+$ git checkout -b branch-1.X origin/master
```
#### 2. Update package version and tag
@@ -48,11 +48,11 @@ $ npm version prerelease --preid=rc
# Confirm that the "candidate" tag has been created
$ git tag -l
-v0.X.0-rc.1
+v1.X.0-rc.1
# Push both the branch and the tag to GitHub repo
-$ git push origin branch-0.X
-$ git push origin v0.X.0-rc.1
+$ git push origin branch-1.X
+$ git push origin v1.X.0-rc.1
```
#### 3. Build and inspect the artifacts
@@ -142,9 +142,9 @@ Send an email on the Pulsar Dev mailing list:
```
To: [email protected]
-Subject: [VOTE] Pulsar Node.js Client Release 0.X.0 Candidate 1
+Subject: [VOTE] Pulsar Node.js Client Release 1.X.0 Candidate 1
-This is the first release candidate for Apache Pulsar Node.js client, version
0.X.0.
+This is the first release candidate for Apache Pulsar Node.js client, version
1.X.0.
It fixes the following issues:
https://github.com/apache/pulsar-client-node/milestone/1?closed=1
@@ -156,11 +156,11 @@ Note that we are voting upon the source (tag), the npm
package is provided
for convenience.
The tag to be voted upon:
-v0.X.0-rc.1
-https://github.com/apache/pulsar-client-node/releases/tag/v0.X.0-rc.1
+v1.X.0-rc.1
+https://github.com/apache/pulsar-client-node/releases/tag/v1.X.0-rc.1
The npm package:
-https://www.npmjs.com/package/pulsar-client/v/0.X.0-rc.1
+https://www.npmjs.com/package/pulsar-client/v/1.X.0-rc.1
Please download the source files, and follow the README to build
and run the Pulsar Node.js client.
@@ -177,10 +177,10 @@ If the release is approved here, we can then proceed to
next step.
Bump to the release version and create the final git tag:
```sh
-$ git checkout branch-0.X
+$ git checkout branch-1.X
$ npm version minor
-$ git push origin branch-0.X
-$ git push origin v0.X.0
+$ git push origin branch-1.X
+$ git push origin v1.X.0
```
Publish the package to the npm registry:
@@ -200,9 +200,9 @@ Once the release artifact is available in the npm registry,
we need to announce
Send an email on these lines:
```
To: [email protected], [email protected], [email protected]
-Subject: [ANNOUNCE] Apache Pulsar Node.js client 0.X.0 released
+Subject: [ANNOUNCE] Apache Pulsar Node.js client 1.X.0 released
-The Apache Pulsar team is proud to announce Apache Pulsar Node.js client
version 0.X.0.
+The Apache Pulsar team is proud to announce Apache Pulsar Node.js client
version 1.X.0.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,