-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
Add rooster
release management configuration and instructions
#8567
Conversation
1. Create a PR with the version and `BREAKING_CHANGES.md` updated | ||
We use an experimental in-house tool for managing releases. | ||
|
||
1. Install `rooster`: `pip install git+https://github.com/zanieb/rooster@main` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the @main
have an effect here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It shouldn't, but until it's on PyPI I might tag versions and pin them as changes are made going forward.
We could drop it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As part of this, should we remove the stuff in .github
that categorizes the auto-generated release notes based on labels?
Done — I kind of like that format maybe I'll change ours to use that eventually :) |
I'd rather not be the only one who can easily generate our changelog entries so I invested some time to get Rooster a bit further along and add instructions.