-
-
Notifications
You must be signed in to change notification settings - Fork 458
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
Document the release process #2371
Conversation
CONTRIBUTING.md
Outdated
|
||
`patch` is sequentially increasing for each stubs release. Reset to `0` if `major.minor` was updated. | ||
|
||
- Use pull request title "Version x.y.z release" by convention. |
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.
I notice now that flaeppe has been using PR title "Prepare for a release `5.0.1`". I don't have strong feelings either way. Except for the fact that the "a" there seems ungrammatical and can be omitted.
bb9de49
to
8f2a4d9
Compare
- Delete all release notes lines containing `by @pre-commit-ci` or `by @dependabot`, as these | ||
are irrelevant for our users. |
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.
Haven't done this for the last few releases. It's an additional manual step, but IMO release notes are too noisy if these are included.
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.
+1 from me
Great that we get a release flow documented |
Tweak phrasing & reorder bullet points.
This is my vision of how the release process looks like.
See rendered Markdown here.
Pinging @flaeppe as the one who has made all the latest releases.
Related issues
5.0.1
#2183 (comment)