File: RELEASE.rst

package info (click to toggle)
labgrid 0.4.1-6
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 2,232 kB
  • sloc: python: 17,045; makefile: 30; sh: 12
file content (111 lines) | stat: -rw-r--r-- 2,481 bytes parent folder | download | duplicates (2)
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
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
Step by step guide to releasing a new labgrid version.

0. Preparations
===============
Clean the `dist/` directory:

.. code-block:: bash

   rm dist/*

Check your commit mail and name:

.. code-block:: bash

   git config --get user.name
   git config --get user.email

1. Freeze Dependencies
======================

Freeze the dependencies into the `requirements.txt` file and update the separate
feature requirements files.
This ensures that known good dependencies are available for every release.

2. Update setup.py Dependencies
===============================

Update the minimum required dependencies in the `setup.py` file.
These are intentionally non restrictive, see `PYPA Discussion
<https://packaging.python.org/discussions/install-requires-vs-requirements/>`_.
A frozen environment is already created in the previous step.

3. Update CHANGES.rst
=====================

Update the `CHANGES.rst` file. This should ideally be done in every pull request,
but its better to check that the `CHANGES.rst` is up to date.
Ensure that no incompatiblities are unlisted and that all major features are
described in a separate section.
It's best to compare against the git log.

4. Bump Version Number
======================

Bump the version number in `CHANGES.rst` and `setup.py`

5. Create a signed Tag
======================

Create a signed tag of the new release.
Your PGP-key has to be available on the computer.

.. code-block:: bash

    git tag -s <your-version-number>

6. Create sdist
===============

Run the following command:

::

   python setup.py sdist

The sdist file will be available in the `dist/` directory.

7. Test upload to pypi dev
==========================

Test the upload by using twine to upload to pypi test service

::

   twine upload --repository-url https://test.pypi.org/legacy/ dist/*

8. Test download from pypi dev
==============================

Test the upload by using pypi dev as a download source

::

   virtualenv -p python3 labgrid-release-<your-version-number>
   source labgrid-release-<your-version-number>/bin/activate
   pip install --index-url https://test.pypi.org/simple/ labgrid

And optionally run the tests:

::

   pip install -r dev-requirements
   pytest tests

9. Upload to pypi
=================

Upload the tested dist file to pypi.

::

   twine upload dist/*

10. Upload the signed tag
==========================

Upload the signed tag to the upstream repository

::

   git push upstream <your-version-number>