File: RELEASING.rst

package info (click to toggle)
pyerfa 1.7.2%2Bds-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 5,652 kB
  • sloc: ansic: 30,690; sh: 4,242; python: 2,349; makefile: 78
file content (33 lines) | stat: -rw-r--r-- 1,120 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
Release instructions
====================

Once the package is ready to release, use ``git tag`` to tag the
release::

    git tag -m <version> <version>

e.g::

    git tag -m v1.7.0 v1.7.0

Here, the version number should generally be the same as that of
the erfa library that is included (and you should make sure the
git submodule ``liberfa/erfa`` is at the correct tag as well).
If there is a need for just the wrappers to be updated, add a
fourth number to the release (e.g., ``1.7.0.1``).

You can also include the ``-s`` flag to sign the tag if you have
PGP keys set up. Then, push the tag to GitHub, e.g.::

    git push upstream v0.1

and the build should happen automatically on Azure pipelines. You can
follow the progress of the build here:

https://dev.azure.com/liberfa/pyerfa/_build

If there are any failures, you can always delete the tag, fix the
issues, tag the release again, and push the tag to GitHub.

See the `OpenAstronomy Azure Pipelines Templates Documentation <https://openastronomy-azure-pipelines.readthedocs.io/en/latest/publish.html>`_
for more details about the Azure Pipelines set-up.