- Make sure every change is written in the changelog.
- Make sure the
Changelog.md
has the correct version number and the release date. - Copy the changelog of this version to
.CurrentChangelog.md
. (Our release CI will take this file as the release notes) - Create a pull request, make sure the CI are all passed, and merge it.
- In this step, the main features are completed. No more major feature will be merged after the first Alpha pre-release.
- Use git tag to create a new release tag
major.minor.patch-alpha.version
. And push this tag to GitHub. - Wait for the CI builds and pushes the release binaries and release notes to the GitHub release page.
- Check the
Pre-release
checkbox and publish the pre-release.
- This step is for the issue fixing. No more feature will be accepted.
- Use git tag to create a new release tag
major.minor.patch-beta.version
. And push this tag to GitHub. - Wait for the CI builds and pushes the release binaries and release notes to the GitHub release page.
- Check the
Pre-release
checkbox and publish the pre-release.
- In this step, the issue fixing is finished. The
RC
pre-releases are for the installation, bindings, and packages testing. - Use git tag to create a new release tag
major.minor.patch-rc.version
. And push this tag to GitHub. - Wait for the CI builds and pushes the release binaries and release notes to the GitHub release page.
- Check the
Pre-release
checkbox and publish the pre-release.
- Make sure the
Changelog.md
and.CurrentChangelog.md
have the correct version number and the release date. - Use git tag to create a new release tag
major.minor.patch
. And push this tag to GitHub. - Wait for the CI builds and pushes the release binaries and release notes to the GitHub release page.
- Publish the release.
The following projects will be updated with the Alpha
, Beta
, and RC
pre-releases and the official release: