8000 add release process to docs · ManuelVoiden/document-api-python@6177826 · GitHub
[go: up one dir, main page]

Skip to content

Commit 6177826

Browse files
committed
add release process to docs
1 parent 5ddf93f commit 6177826

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

docs/docs/contributing.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,3 +56,12 @@ For all other things, please submit a PR that includes the fix, documentation, o
5656
If the feature is complex or has multiple solutions that could be equally appropriate approaches, it would be helpful to file an issue to discuss the
5757
design trade-offs of each solution before implementing, to allow us to collectively arrive at the best solution, which most likely exists in the middle
5858
somewhere.
59+
60+
61+
## Release process
62+
63+
We expect that everything merged into the development branch is ready to release on master. Releases can be made at any time - ideally it would be on a regular cadence but currently it is basically on request.
64+
- bump the version in setup.py
65+
- update the changelog: all commits to development should contain a meaningful message, the changelog can be built from these
66+
- merge to master.
67+
This kicks off an automated release in github and then publish to pypi.

0 commit comments

Comments
 (0)
0