You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update the release process to update the release note on pulsar-site (#1375)
### Motivation
In the release process, we don't update go client release note no the pulsar-site: https://pulsar.apache.org/release-notes/client-go/. This makes the pulsar-site go client release note page outdated.
### Modifications
- Update the release process to update the release note on pulsar-site
- Fix ToC
Copy file name to clipboardExpand all lines: docs/release-process.md
+12-11Lines changed: 12 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -5,12 +5,11 @@ In general, you need to perform the following steps:
5
5
1. Create a release branch.
6
6
2. Update the version and tag of a package.
7
7
3. Build and inspect an artifact.
8
-
4. Sign and stage the artifacts.
9
-
5. Write a release note.
10
-
6. Run a vote.
11
-
7. Promote the release.
12
-
8. Update the release note.
13
-
9. Announce the release.
8
+
4. Write a release note.
9
+
5. Run a vote.
10
+
6. Promote the release.
11
+
7. Update the release note.
12
+
8. Announce the release.
14
13
15
14
### Requirements
16
15
-[Creating GPG keys to sign release artifacts](https://pulsar.apache.org/contribute/create-gpg-keys/)
@@ -78,13 +77,13 @@ $ svn ci -m 'Staging artifacts and signature for Pulsar Client Go release 0.X.0-
78
77
79
78
Since this needs to be merged in master, we need to follow the regular process and create a Pull Request on GitHub.
80
79
81
-
5. Write a release note and update `CHANGELOG.md`.
80
+
4. Write a release note and update `CHANGELOG.md`.
82
81
83
82
Check the milestone in GitHub associated with the release.
84
83
85
84
In the released item, add the list of the most important changes that happened in the release and a link to the associated milestone, with the complete list of all the changes.
86
85
87
-
6. Run a vote.
86
+
5. Run a vote.
88
87
89
88
Send an email to the Pulsar Dev mailing list:
90
89
@@ -127,7 +126,7 @@ The vote should be open for at least 72 hours (3 days). Votes from Pulsar PMC me
127
126
128
127
If the release is approved here, we can then proceed to the next step.
129
128
130
-
7. Promote the release.
129
+
6. Promote the release.
131
130
132
131
```
133
132
$ git checkout branch-0.X.0
@@ -155,11 +154,13 @@ svn ls https://dist.apache.org/repos/dist/release/pulsar | grep client-go
Add the release note to [Pulsar Client Go](https://github.com/apache/pulsar-client-go/releases)
161
160
162
-
9. Announce the release.
161
+
Add the release note to the [Pulsar Website](https://pulsar.apache.org/release-notes/client-go/). Here is an example PR: https://github.com/apache/pulsar-site/pull/1016
162
+
163
+
8. Announce the release.
163
164
164
165
Once the release process is available , you can announce the release and send an email as below:
0 commit comments