Skip to content

Commit ad9a7d1

Browse files
authored
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
1 parent f673e4d commit ad9a7d1

File tree

1 file changed

+12
-11
lines changed

1 file changed

+12
-11
lines changed

docs/release-process.md

Lines changed: 12 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,11 @@ In general, you need to perform the following steps:
55
1. Create a release branch.
66
2. Update the version and tag of a package.
77
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.
1413

1514
### Requirements
1615
- [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-
7877

7978
Since this needs to be merged in master, we need to follow the regular process and create a Pull Request on GitHub.
8079

81-
5. Write a release note and update `CHANGELOG.md`.
80+
4. Write a release note and update `CHANGELOG.md`.
8281

8382
Check the milestone in GitHub associated with the release.
8483

8584
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.
8685

87-
6. Run a vote.
86+
5. Run a vote.
8887

8988
Send an email to the Pulsar Dev mailing list:
9089

@@ -127,7 +126,7 @@ The vote should be open for at least 72 hours (3 days). Votes from Pulsar PMC me
127126

128127
If the release is approved here, we can then proceed to the next step.
129128

130-
7. Promote the release.
129+
6. Promote the release.
131130

132131
```
133132
$ git checkout branch-0.X.0
@@ -155,11 +154,13 @@ svn ls https://dist.apache.org/repos/dist/release/pulsar | grep client-go
155154
svn rm https://dist.apache.org/repos/dist/release/pulsar/pulsar-client-go/pulsar-client-go-0.X.0
156155
```
157156

158-
8. Update the release note.
157+
7. Update the release note.
159158

160159
Add the release note to [Pulsar Client Go](https://github.com/apache/pulsar-client-go/releases)
161160

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.
163164

164165
Once the release process is available , you can announce the release and send an email as below:
165166

0 commit comments

Comments
 (0)