-
-
Notifications
You must be signed in to change notification settings - Fork 419
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
Release template purposal #543
Labels
Comments
We can reuse placeholder here https://github.com/requests/requests-oauthlib/blob/master/docs/contributing.rst?plain=1#L61 |
This is a great place to document, we can flesh this deployment/releases section out for now and see how that serves the community/maintainers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Considering the many moving parts of the release process and integration with the PyPi, it would be beneficial to create some sort of release protection or employ a template. I have not researched this specifically but wanted to open the conversation here on this issue to explore the possibilities.
Some specific things to consider could be creating a check list or template guiding team members to:
I imagine there are other points to cover.
Feedback highly encourage, positive/critical any and all welcome.
The text was updated successfully, but these errors were encountered: