Skip to content

Commit e804eed

Browse files
committed
Rework development doc
1 parent 87e478e commit e804eed

File tree

1 file changed

+16
-18
lines changed

1 file changed

+16
-18
lines changed

docs/development.rst

Lines changed: 16 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ First, take the time to look into our GitHub `issues`_ tracker if
1818
this already covered. If not, changes are good that we avoid double work.
1919

2020

21-
Fixing Bugs and Implementing New Features
22-
-----------------------------------------
21+
Prerequisites
22+
-------------
2323

2424
Before you make changes to the code, we would highly appreciate if you
2525
consider the following general requirements:
@@ -29,12 +29,6 @@ consider the following general requirements:
2929
* Check if your feature is covered by the Semantic Versioning specification.
3030
If not, ask on its GitHub project https://github.com/semver/semver.
3131

32-
* Write test cases if you implement a new feature.
33-
34-
* Test also for side effects of your new feature and run the complete
35-
test suite.
36-
37-
* Document the new feature, see :ref:`doc` for details.
3832

3933

4034
Modifying the Code
@@ -61,20 +55,23 @@ We recommend the following workflow:
6155

6256
$ git checkout -b feature/NAME_OF_YOUR_FEATURE
6357

64-
#. Work on your branch. Commit your work.
58+
#. Work on your branch and create a pull request:
6559

66-
#. Write test cases and run the test suite, see :ref:`testsuite` for details.
60+
a. Write test cases and run the complete test suite, see :ref:`testsuite`
61+
for details.
6762

68-
#. Create a `pull request`_. Describe in the pull request what you did
69-
and why. If you have open questions, ask.
63+
b. Write a changelog entry, see section :ref:`changelog`.
7064

71-
#. Wait for feedback. If you receive any comments, address these.
65+
c. If you have implemented a new feature, document it into our
66+
documentation to help our reader. See section :ref:`doc` for
67+
further details.
7268

73-
#. After your pull request got accepted, delete your branch.
69+
d. Create a `pull request`_. Describe in the pull request what you did
70+
and why. If you have open questions, ask.
7471

75-
#. Use the ``clean`` command to remove build and test files and folders::
72+
#. Wait for feedback. If you receive any comments, address these.
7673

77-
$ python setup.py clean
74+
#. After your pull request got accepted, delete your branch.
7875

7976

8077
.. _testsuite:
@@ -227,8 +224,8 @@ documentation includes:
227224

228225
.. _changelog:
229226

230-
Changelog
231-
---------
227+
Adding a Changelog Entry
228+
------------------------
232229

233230
.. include:: ../changelog.d/README.rst
234231
:start-after: -text-begin-
@@ -241,3 +238,4 @@ Changelog
241238
.. _Semantic Versioning: https://semver.org
242239
.. _Sphinx style: https://sphinx-rtd-tutorial.readthedocs.io/en/latest/docstrings.html
243240
.. _tox: https://tox.readthedocs.org/
241+

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy