-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Release Process
Max Katz edited this page Mar 21, 2024
·
6 revisions
Backporting:
- Go through PRs with "backport-candidate-*" tags, make sure this list makes sense.
- Checkout https://github.com/grokys/avalonia-backport tool from the source code, get github api token.
- Checkout stable release branch, like
release/11.0
. - Run backport checrry-picking process to the stable release branch.
- Test if everything builds and tests are passing.
- Test nightly builds of Avalonia.
- Run labeling process (automatically replace "backport-candidate" with "backported" tags) and generate changelog.
Releasing:
- Create a branch named
release/11.0.9
for specific minor version. - Update the version number in the file
SharedVersion.props
i.e.<Version>11.0.9</Version>
. - Add
11.0.9
tag for this version. - Push the release branch and the tag.
- Wait for azure pipelines to finish the build. Nightly build with
11.0.9
version should be released soon after. - Using the nightly build run a due diligence test to make sure you're happy with the package.
- On azure pipelines, on the release for your release branch
release/11.0.9
click on the badge for "Nuget Release" - Click deploy
- Make a release on Github releases, this will set a tag named:
11.0.9
for you. - Press "Auto-generate changelog", so GitHub will append information about new contributors.
- Replace changelog with one generated by
avalonia-backport
tool. Enable discussion for the specific release. - Review the release information and publish.
- Update the dotnet templates, visual studio templates.
- Announce on telegram (RU and EN), twitter, etc