diff --git a/CHANGES.md b/CHANGES.md index e21905e6f..8d112cb0a 100644 --- a/CHANGES.md +++ b/CHANGES.md @@ -1,16 +1,9 @@ Full changelog ============== -v1.4.0 (2022-05-31) +v1.5.0 (2022-06-28) ------------------- -* Add support for specifying visual attributes when creating a subset group. [#2297] - -* Modify profile viewer so that when in 'Sum' mode, parts of profiles - with no valid values are NaN rather than zero. [#2298] - -* Add support for using degrees in full-sphere projections. [#2279] - * Fixed a bug on setting a return view in `compute_statistic` when a subset is defined, resulting in a broadcast error in arrays large enough to need chunking. [#2302] @@ -19,6 +12,17 @@ v1.4.0 (2022-05-31) to be set on instantiation or modified using the ``rotate_to`` and ``rotate_by`` methods. [#2235] + +v1.4.0 (2022-05-31) +------------------- + +* Add support for specifying visual attributes when creating a subset group. [#2297] + +* Modify profile viewer so that when in 'Sum' mode, parts of profiles + with no valid values are NaN rather than zero. [#2298] + +* Add support for using degrees in full-sphere projections. [#2279] + v1.3.0 (2022-04-22) ------------------- diff --git a/RELEASE.rst b/RELEASE.rst new file mode 100644 index 000000000..cbdb43d87 --- /dev/null +++ b/RELEASE.rst @@ -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 `_ + 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.