You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@opendal.apache.org by "markt-asf (via GitHub)" <gi...@apache.org> on 2023/08/01 12:00:44 UTC
[GitHub] [incubator-opendal] markt-asf commented on pull request #2729: docs: auto relaese maven artifacts
markt-asf commented on PR #2729:
URL: https://github.com/apache/incubator-opendal/pull/2729#issuecomment-1660168845
The review checklist needs to include checking that the release is repeatable.
If the release fails and you tag a new version, why do you need to use rcN version numbers at all?
If you want to use multiple release candidates then the process would be something like:
- set version to X.Y.Z
- tag X.Y.Z-RCN in GitHub
- let CI do its thing
- upload the RC to the various ASF locations (dist, Maven staging)
- VOTE
- if vote fails, repeat from step 1 with RCN => RC(N+1)
- if vote passes, publish releases
- copy final X.Y.Z-RC? tag to X.Y.Z
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org