New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document release process #206

Open

lann opened this issue Sep 27, 2023 · 0 comments

Assignees

Collaborator

lann commented Sep 27, 2023 •

edited

Probably won't be much more than proposed here for 0.2.0, but getting it written down in the repo would be good:

Cut a release-0.2 branch from main
Update main Cargo.toml version = "0.3.0-dev"
In the release-0.2 branch:
- Finalize 0.2.0 release:
  - Feature freeze / bug fix period (if desired)
  - Update changelog (if we want one in-tree)
- PR/merge Cargo.toml version = "0.2.0"
- Tag that commit as v0.2.0

The text was updated successfully, but these errors were encountered:

lann self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment