-
Notifications
You must be signed in to change notification settings - Fork 153
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Preparing release v1.5.0; add instructions
- Loading branch information
Showing
3 changed files
with
42 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
How to release a new version of Glue | ||
==================================== | ||
|
||
#. Edit the ``CHANGES.rst`` file to add the release date for the release | ||
you want to make and make sure the changelog is complete. | ||
|
||
#. Commit the changes using:: | ||
|
||
git commit -m "Preparing release v..." | ||
|
||
where v... is the version you are releasing and push to main:: | ||
|
||
git push upstream main | ||
|
||
#. Tag the release you want to make, optionally signing it (``-s``):: | ||
|
||
git tag -m v1.5.1 v1.5.1 | ||
|
||
and push the tag:: | ||
|
||
git push upstream v1.5.1 | ||
|
||
#. At this point, the release sdist and wheel will be built on by GitHub | ||
Actions and automatically uploaded to PyPI. You can check the build | ||
for the release commit `here <https://github.com/glue-viz/glue/actions/>`_ | ||
and if there are any issues you can delete the tag, fix the issues | ||
(preferably via a pull request) and then try the release process | ||
again. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters