-
Notifications
You must be signed in to change notification settings - Fork 423
Release process
Yossi Itigin edited this page Dec 3, 2021
·
17 revisions
- Create release branch
v<major>.<minor>.x
- Bump version of master branch
- Update NEWS on the release branch
- Mention items that affect user experience (feature/bugfix/enhancement), or key infrastructure changes
- Go over commit titles excluding merge commits since the previous release and add relevant items
git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr)%Creset' --abbrev-commit --date=relative master..branch-X
- Add items from internal checklists, such as Plan-of-Record
- Tag key community members in the new PR to add/modify missing items
- Update Author list before release
git log --pretty=format:"%an%x09%ae" | sort | uniq > AUTHORS.new
- since people use multiple email addresses and names we have to clean up the new file
vimdiff AUTHORS.new AUTHORS
https://github.com/openucx/ucx/wiki/UCX-release-checklist
- Go to Code->Releases
- Click Draft new release
- Set the release version, target branch, and mark as pre-release (for release candidate)
-
Click Publish Release
-
An automatic Azure pipeline will start building the packages, please Do not touch the release page while the job is running
-
When step (5) finishes, there will be a new release page with all packages attached to it
-
Remove excess news from the release page
-
Send an email to ucx-dev mailing list to announce the release