This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/qpid-proton.git
The following commit(s) were added to refs/heads/main by this push:
new 8d3597080 NO-JIRA: refresh releasing doc
8d3597080 is described below
commit 8d359708048ddd065ea71eb23de219014cf89e2c
Author: Robbie Gemmell <[email protected]>
AuthorDate: Mon Aug 17 11:02:49 2026 +0100
NO-JIRA: refresh releasing doc
---
docs/release.md | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/docs/release.md b/docs/release.md
index 4f31ba157..939fa1259 100644
--- a/docs/release.md
+++ b/docs/release.md
@@ -13,18 +13,19 @@
- e.g "gpg --detach-sign --armor qpid-proton-${VERSION}.tar.gz"
- e.g "sha512sum qpid-proton-${VERSION}.tar.gz >
qpid-proton-${VERSION}.tar.gz.sha512"
7. Push branch changes and tag.
- - Also update versions to the applicable snapshot version for future work on
it.
+ - Also update versions again to the applicable next -dev version for future
work on it.
8. Commit artifacts to dist dev repo in
https://dist.apache.org/repos/dist/dev/qpid/proton/${TAG} dir.
9. Send vote email, provide links to dist dev repo and JIRA release notes.
### After a vote succeeds:
-1. Tag the RC with the final version.
+1. Tag the RC commit with the final version.
+ - Run: 'git tag -m "Release ${VERSION}" ${VERSION}', e.g: git tag -m
"Release 0.18.0" 0.18.0
2. Add the artifacts to dist release repo:
svn cp -m "add files for qpid-proton-${VERSION}"
https://dist.apache.org/repos/dist/dev/qpid/proton/${TAG}
https://dist.apache.org/repos/dist/release/qpid/proton/${VERSION}
-3. Give the mirrors some time to distribute things. Can take 24hrs for good
coverage.
- - Status is visible at: https://www.apache.org/mirrors/
+3. Give the some time to distribute things to downloads.apache.org and the
CDN. Typically takes ~15mins.
+ - Content is viewable under: https://downloads.apache.org/qpid/proton/ and
https://dlcdn.apache.org/qpid/proton/
4. Update the website with release content.
5. Send release announcement email.
6. Clean out older release(s) from release repo as appropriate.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
