Skip to content

Commit b1d1f4f

Browse files
committed
better development docs
1 parent 86aabcd commit b1d1f4f

1 file changed

Lines changed: 20 additions & 20 deletions

File tree

doc/development.rst

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -27,23 +27,6 @@ The following assumes that the commands are executed from the root of the reposi
2727
makes Sphinx complain about more subtle problems.
2828

2929

30-
Creating a Release
31-
------------------
32-
33-
- Release from the ``master`` branch.
34-
- Update the library version in ``__init__.py`` using `semantic versioning <http://semver.org>`__.
35-
- Run all tests and examples against available hardware.
36-
- Update `CONTRIBUTORS.txt` with any new contributors.
37-
- Sanity check that documentation has stayed inline with code. For large changes update ``doc/history.rst``
38-
- Create a temporary virtual environment. Run ``python setup.py install`` and ``python setup.py test``
39-
- Create and upload the distribution: ``python setup.py sdist bdist_wheel``
40-
- Sign the packages with gpg ``gpg --detach-sign -a dist/python_can-X.Y.Z-py3-none-any.whl``
41-
- Upload with twine ``twine upload dist/python-can-X.Y.Z*``
42-
- In a new virtual env check that the package can be installed with pip: ``pip install python-can==X.Y.Z``
43-
- Create a new tag in the repository.
44-
- Check the release on PyPi, readthedocs and github.
45-
46-
4730
Code Structure
4831
--------------
4932

@@ -56,13 +39,30 @@ The modules in ``python-can`` are:
5639
+---------------------------------+------------------------------------------------------+
5740
|:doc:`bus <bus>` | Contains the interface independent Bus object. |
5841
+---------------------------------+------------------------------------------------------+
59-
|:doc:`CAN <api>` | Contains modules to emulate a CAN system, such as a |
60-
| | time stamps, read/write streams and listeners. |
61-
+---------------------------------+------------------------------------------------------+
6242
|:doc:`message <message>` | Contains the interface independent Message object. |
6343
+---------------------------------+------------------------------------------------------+
6444
|:doc:`io <listeners>` | Contains a range of file readers and writers. |
6545
+---------------------------------+------------------------------------------------------+
6646
|:doc:`broadcastmanager <bcm>` | Contains interface independent broadcast manager |
6747
| | code. |
6848
+---------------------------------+------------------------------------------------------+
49+
|:doc:`CAN <api>` | Legacy API. Depecated. |
50+
+---------------------------------+------------------------------------------------------+
51+
52+
53+
Creating a new Release
54+
----------------------
55+
56+
- Release from the ``master`` branch.
57+
- Update the library version in ``__init__.py`` using `semantic versioning <http://semver.org>`__.
58+
- Run all tests and examples against available hardware.
59+
- Update `CONTRIBUTORS.txt` with any new contributors.
60+
- For larger changes update ``doc/history.rst``.
61+
- Sanity check that documentation has stayed inline with code.
62+
- Create a temporary virtual environment. Run ``python setup.py install`` and ``python setup.py test``
63+
- Create and upload the distribution: ``python setup.py sdist bdist_wheel``
64+
- Sign the packages with gpg ``gpg --detach-sign -a dist/python_can-X.Y.Z-py3-none-any.whl``
65+
- Upload with twine ``twine upload dist/python-can-X.Y.Z*``
66+
- In a new virtual env check that the package can be installed with pip: ``pip install python-can==X.Y.Z``
67+
- Create a new tag in the repository.
68+
- Check the release on PyPi, Read the docs and GitHub.

0 commit comments

Comments
 (0)