contributing.rst guide: Make the rules reflect the reality.
This commit is contained in:
parent
17bbce7c8a
commit
765ff4b67b
1 changed files with 7 additions and 2 deletions
|
|
@ -349,8 +349,13 @@ General commit rules
|
||||||
--------------------
|
--------------------
|
||||||
|
|
||||||
1. The commit message should contain either ``[bugfix]`` or ``[feature]``
|
1. The commit message should contain either ``[bugfix]`` or ``[feature]``
|
||||||
or ``[refactoring]`` or ``[other]``. Refactorings and bugfixes and "other"
|
or ``[refactoring]`` or ``[other]``. In practice however this is very
|
||||||
are backported to the latest stable release branch (currently 0.20.x).
|
often forgotten and a commit message like ``fixes #xyz`` is good enough.
|
||||||
|
|
||||||
|
Every commit is backported unless
|
||||||
|
tagged with either ``[feature]`` or with ``[nobackport]``. They are
|
||||||
|
backported to the latest stable release branch (currently 0.20.x).
|
||||||
|
|
||||||
Refactorings are backported because they often enable further bugfixes.
|
Refactorings are backported because they often enable further bugfixes.
|
||||||
|
|
||||||
2. If you introduce changes which affect backwards compatibility,
|
2. If you introduce changes which affect backwards compatibility,
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue