Release process

Preparations

1. Create release branch v<major>.<minor>.x
2. Bump version of master branch
3. Update NEWS on the release branch
   1. Mention items that affect user experience (feature/bugfix/enhancement), or key infrastructure changes
   2. Go over commit titles excluding merge commits since the previous release and add relevant items
   3. NEWS should be updated for every release candidate git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr)%Creset' --abbrev-commit --date=relative master..branch-X
   4. Add items from internal checklists, such as Plan-of-Record
   5. Tag key community members in the new PR to add/modify missing items
4. Update Author list before release
   1. git log --pretty=format:"%an%x09%ae" | sort | uniq > AUTHORS.new
   2. since people use multiple email addresses and names we have to clean up the new file
      vimdiff AUTHORS.new AUTHORS

Original release notes (can be deleted once we close on this one)

https://github.com/openucx/ucx/wiki/UCX-release-checklist

Publishing releases

1. Go to Code->Releases

2. Click Draft new release

3. Set the release version, target branch, and mark as pre-release (for release candidate)

4. Click Publish Release

5. An automatic Azure pipeline will start building the packages, please Do not touch the release page while the job is running

6. When step (5) finishes, there will be a new release page with all packages attached to it

7. Remove excess news from the release page

8. Send an email to ucx-dev mailing list to announce the release