Hacking manual: documented how to create tags
Signed-off-by: Eygene Ryabinkin <rea@codelabs.ru>
This commit is contained in:
parent
d2ec2a4e9e
commit
ee89610f3a
@ -120,6 +120,15 @@ A typical release cycle works like this:
|
|||||||
|
|
||||||
5. When we think a release is stable enough, we restart from step 1.
|
5. When we think a release is stable enough, we restart from step 1.
|
||||||
|
|
||||||
|
Tagging release or RC
|
||||||
|
---------------------
|
||||||
|
|
||||||
|
It is done via Git's ``tag`` command, but you must do ``git tag -a``
|
||||||
|
to create annotated tag.
|
||||||
|
|
||||||
|
Release tags are named ``vX.Y.Z`` and release candidate tags are named
|
||||||
|
``vX.Y.Z-rcN``.
|
||||||
|
|
||||||
|
|
||||||
.. _contribution checklist:
|
.. _contribution checklist:
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user