Am 2022-10-30 um 12:04 schrieb Slawomir Jaranowski:
Hi,
Current procedure of releases is unclear in case of restart releases. [1]
I see two cases:
- technical problem during release ... something goes wrong after SMC tag
was created
- canceled vote
Technically we have many solutions:
1.
- drop old tag and restart with the same version
- no need other actions
2.
- restart process with next version
- don't touch wrong tag in repo
- or drop old tag
- rename release label in jira
- or create next release and add only fixed issues for restart
[1]
https://maven.apache.org/developers/release/maven-project-release-procedure.html#check-the-vote-results
Let me describe I have done and likely others for the past 10 years:
Vote has been canceled:
1. Drop staging repo
2. create version n + 1 in JIRA
3. Archive version n in JIRA
4. Assign issues from version n also to version n + 1
5. Don't touch tag in Git repo
6. Fix found issues and assign them to version n + 1
7. start new release process
With this you can:
1. Always trace down the canceled release by source and issues
2. Make clear via ML that release is defunct
Note that versions are cheap and one should rather distinct versions
than having two different source releases under the same tag/name.
Here is an example:
https://issues.apache.org/jira/projects/SCM/versions/12350866
M
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
