@@ -34,20 +34,20 @@ To install from source on github_::
3434Release
3535-------
3636
37- x . Test and commit changes
38- x . Merge your changes
39- x . Go to main page for repo
40- x . Click “Releases” on right side of screen
41- x . Click “Draft a new release” button on top of screen
42- x . For the tag, make a new tag with the new version number
43- x . You can generate the release notes via the “generate release notes” button,
37+ # . Test and commit changes
38+ # . Merge your changes
39+ # . Go to main page for repo
40+ # . Click “Releases” on right side of screen
41+ # . Click “Draft a new release” button on top of screen
42+ # . For the tag, make a new tag with the new version number
43+ # . You can generate the release notes via the “generate release notes” button,
4444 comparing against the most recent release. This will autofill in the details
4545 for you
46- x . Click “Publish release”
46+ # . Click “Publish release”
4747 - This will trigger the workflow to push a new release to PyPI, assuming no
4848 problems have snuck into our release procedure since the last time it was
4949 run
50- x . Open a PR bumping the version to the next version number so that we’re ready
50+ # . Open a PR bumping the version to the next version number so that we’re ready
5151 for the next change. This should always be the first PR in a new release
5252 (otherwise we’ll have build issues), so it should be straight-forward to
5353 figure out how to do this
0 commit comments