diff options
| author | Andreas Rumpf <rumpf_a@web.de> | 2019-06-07 16:21:01 +0200 |
|---|---|---|
| committer | Andreas Rumpf <rumpf_a@web.de> | 2019-06-07 16:21:01 +0200 |
| commit | 2c03c9f42e882eaff4f8e8fa358b9c66ecdd803a (patch) | |
| tree | acfb61e3aa1df55934cb0592f1c34632b045712f /doc | |
| parent | 99a4fed96b4e703ff490edfaa65e0832ad41ce34 (diff) | |
| download | Nim-2c03c9f42e882eaff4f8e8fa358b9c66ecdd803a.tar.gz | |
updates the contributing guidelines [other]
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/contributing.rst | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/doc/contributing.rst b/doc/contributing.rst index c240cb80e..317fe3ab7 100644 --- a/doc/contributing.rst +++ b/doc/contributing.rst @@ -343,12 +343,10 @@ The Git stuff General commit rules -------------------- -1. Bugfixes that should be backported to the latest stable release should - contain the string ``[backport]`` in the commit message! There will be an - outmated process relying on these. However, bugfixes also have the inherent - risk of causing regressions which are worse for a "stable, bugfixes-only" - branch, so in doubt, leave out the ``[backport]``. Standard library bugfixes - are less critical than compiler bugfixes. +1. The commit message should contain either ``[bugfix]`` or ``[feature]`` + or ``[refactoring]`` or ``[other]``. Refactorings and bugfixes and "other" + are backported to the latest stable release branch (currently 0.20.x). + Refactorings are backported because they often enable further bugfixes. 2. All changes introduced by the commit (diff lines) must be related to the subject of the commit. |