gimmecert Changeset - 0825b8a81f60

Changeset - 0825b8a81f60

Parent rev.

Child rev.

[Not reviewed]

0 1 0

Branko Majic (branko) - 6 years ago 2018-05-13 22:34:32
branko@majic.rs

GC-24: Updated naming convention for maintenance branches in development documentation.

1 file changed with 5 insertions and 5 deletions:

docs/development.rst

0 comments (0 inline, 0 general)

docs/development.rst

➞

Show inline comments

@@ @@ -157,7 +157,7 @@ Versioning schema @@
 -----------------
 Project employs `semantic versioning <http://semver.org/>`_ schema. In
- short:
 short:
 - Each version is composed of major, minor, and patch number. For example, in
   version ``1.2.3``, ``1`` is the major, ``2`` is the minor, and ``3`` is the
@@ @@ -182,10 +182,10 @@ nomenclature for naming the branches: @@
   preview purposes.
 - Patch releases are based off the maintenance branches. Mainteance
   branches are named after the ``MAJOR`` and ``MINOR`` number of the
   version - ``MAJOR.MINOR``. For example, if a new release is made
   with version ``1.2.0``, the corresponding branch that is created for
   maintenance will be named ``1.2`` (notice the absence of ``.0`` at
   the end).
   version - ``maintenance/MAJOR.MINOR``. For example, if a new release
   is made with version ``1.2.0``, the corresponding branch that is
   created for maintenance will be named ``maintenance/1.2`` (notice the absence of
   ``.0`` at the end).
 Backporting fixes

0 comments (0 inline, 0 general)