44Release notes
55=============
66
7+ Introduction
8+ ~~~~~~~~~~~~
9+
710Kayobe (just like Kolla) uses the following release notes sections:
811
912- ``features`` --- for new features or functionality; these should ideally
@@ -22,7 +25,7 @@ Other release note types may be applied per common sense.
2225Each change should include a release note unless being a ``TrivialFix``
2326change or affecting only docs or CI. Such changes should `not` include
2427a release note to avoid confusion.
25- Remember release notes are mostly for end users which, in case of Kolla ,
28+ Remember release notes are mostly for end users which, in case of Kayobe ,
2629are OpenStack administrators/operators.
2730In case of doubt, the core team will let you know what is required.
2831
@@ -33,13 +36,106 @@ To add a release note, run the following command:
3336 tox -e venv -- reno new <summary-line-with-dashes>
3437
3538All release notes can be inspected by browsing ``releasenotes/notes``
36- directory.
39+ directory. Further on this page we show reno templates, examples and how to
40+ make use of them.
41+
42+ .. note::
3743
38- To generate release notes in HTML format in ``releasenotes/build``, run:
44+ The term `release note` is often abbreviated to `reno` as it is the name of
45+ the tool that is used to manage the release notes.
46+
47+ To generate renos in HTML format in ``releasenotes/build``, run:
3948
4049.. code-block:: console
4150
4251 tox -e releasenotes
4352
4453Note this requires the release note to be tracked by ``git`` so you
4554have to at least add it to the ``git``'s staging area.
55+
56+ Templates and examples
57+ ~~~~~~~~~~~~~~~~~~~~~~
58+
59+ All approved release notes end up being published on a dedicated site:
60+
61+ https://docs.openstack.org/releasenotes/kayobe/
62+
63+ When looking for examples, it is advised to consider browsing the page above
64+ for a similar type of change and then comparing with their source
65+ representation in ``releasenotes/notes``.
66+
67+ The sections below give further guidelines. Please try to follow them but note
68+ they are not set in stone and sometimes a different wording might be more
69+ appropriate. In case of doubt, the core team will be happy to help.
70+
71+ Features
72+ --------
73+
74+ Template
75+ ++++++++
76+
77+ .. path releasenotes/templates/feature.yml
78+ .. code-block:: yaml
79+
80+ ---
81+ features:
82+ - |
83+ Implements [some feature].
84+ [Can be described using multiple sentences if necessary.]
85+
86+ Example
87+ +++++++
88+
89+ Implementing feature with id `letsencrypt-https`, we use ``reno`` to generate
90+ the scaffolded file:
91+
92+ .. code-block:: console
93+
94+ tox -e venv -- reno new --from-template releasenotes/templates/feature.yml letsencrypt-https
95+
96+ And then fill it out with the following content (for example):
97+
98+ .. code-block:: yaml
99+
100+ ---
101+ features:
102+ - |
103+ Implements support for hassle-free integration with Let's Encrypt.
104+ The support is limited to operators in the underworld.
105+ For more details check the TLS docs of Kayobe.
106+
107+ Fixes
108+ -----
109+
110+ Template
111+ ++++++++
112+
113+ .. path releasenotes/templates/fix.yml
114+ .. code-block:: yaml
115+
116+ ---
117+ fixes:
118+ - |
119+ Fixes [some bug].
120+ [Can be described using multiple sentences if necessary.]
121+ [Possibly also giving the previous behaviour description.]
122+ `LP#[bug number] <https://bugs.launchpad.net/kayobe/+bug/[bug number]>`__
123+
124+ Example
125+ +++++++
126+
127+ Fixing bug number `9999999`, we use ``reno`` to generate the scaffolded file:
128+
129+ .. code-block:: console
130+
131+ tox -e venv -- reno new --from-template releasenotes/templates/fix.yml bug-9999999
132+
133+ And then fill it out with the following content (for example):
134+
135+ .. code-block:: yaml
136+
137+ ---
138+ fixes:
139+ - |
140+ Fixes ``deploy-containers`` action missing for the Masakari role.
141+ `LP#9999999 <https://bugs.launchpad.net/kayobe/+bug/9999999>`__
0 commit comments