|
| 1 | +Contributing |
| 2 | +============ |
| 3 | + |
| 4 | +If you find bugs, errors, omissions or other things that need improvement, |
| 5 | +please create an issue or a pull request at |
| 6 | +https://github.com/spatialaudio/python-rtmixer/. |
| 7 | +Contributions are always welcome! |
| 8 | + |
| 9 | + |
| 10 | +Development Installation |
| 11 | +------------------------ |
| 12 | + |
| 13 | +Instead of pip-installing the latest release from PyPI_, you should get the |
| 14 | +newest development version (a.k.a. "master") with Git:: |
| 15 | + |
| 16 | + git clone https://github.com/spatialaudio/python-rtmixer.git --recursive |
| 17 | + cd python-rtmixer |
| 18 | + python3 -m pip install -e . --user |
| 19 | + |
| 20 | +... where ``-e`` stands for ``--editable``. |
| 21 | + |
| 22 | +When installing this way, you can quickly try other Git |
| 23 | +branches (in this example the branch is called "another-branch"):: |
| 24 | + |
| 25 | + git checkout another-branch |
| 26 | + |
| 27 | +If you want to go back to the "master" branch, use:: |
| 28 | + |
| 29 | + git checkout master |
| 30 | + |
| 31 | +To get the latest changes from Github, use:: |
| 32 | + |
| 33 | + git pull --ff-only |
| 34 | + |
| 35 | +If you used the ``--recursive`` option when cloning, |
| 36 | +the ``portaudio`` submodule (which is needed for compiling the module) |
| 37 | +will be checked out automatically. |
| 38 | +If not, you can get the submodule with:: |
| 39 | + |
| 40 | + git submodule update --init |
| 41 | + |
| 42 | +.. _PyPI: https://pypi.org/project/python-rtmixer/ |
| 43 | + |
| 44 | + |
| 45 | +Building the Documentation |
| 46 | +-------------------------- |
| 47 | + |
| 48 | +If you make changes to the documentation, you should create the HTML |
| 49 | +pages locally using Sphinx and check if they look OK. |
| 50 | + |
| 51 | +Initially, you might need to install a few packages that are needed to build the |
| 52 | +documentation:: |
| 53 | + |
| 54 | + python3 -m pip install -r doc/requirements.txt --user |
| 55 | + |
| 56 | +To (re-)build the HTML files, use:: |
| 57 | + |
| 58 | + python3 setup.py build_sphinx |
| 59 | + |
| 60 | +The generated files will be available in the directory ``build/sphinx/html/``. |
| 61 | + |
| 62 | + |
| 63 | +Creating a New Release |
| 64 | +---------------------- |
| 65 | + |
| 66 | +New releases are made using the following steps: |
| 67 | + |
| 68 | +#. Bump version number in ``src/rtmixer.py`` |
| 69 | +#. Update ``NEWS.rst`` |
| 70 | +#. Commit those changes as "Release x.y.z" |
| 71 | +#. Create an (annotated) tag with ``git tag -a x.y.z`` |
| 72 | +#. Push the commit and the tag to Github |
| 73 | +#. Wait 10 minutes for the PyPI packages to be automagically uploaded |
| 74 | +#. On Github, `add release notes`_ containing a |
| 75 | + link to PyPI and the bullet points from ``NEWS.rst`` |
| 76 | +#. Check that the new release was built correctly on RTD_ |
| 77 | + and select the new release as default version |
| 78 | + |
| 79 | +.. _add release notes: https://github.com/spatialaudio/python-rtmixer/tags |
| 80 | +.. _RTD: https://readthedocs.org/projects/python-rtmixer/builds/ |
0 commit comments