Line 0
Link Here
|
|
|
1 |
Reno is a release notes manager designed with high throughput in mind, |
2 |
supporting fast distributed development teams without introducing additional |
3 |
development processes. The goal is to encourage detailed and accurate release |
4 |
notes for every release. |
5 |
|
6 |
Reno uses git to store its data, along side the code being described. This means |
7 |
release notes can be written when the code changes are fresh, so no details are |
8 |
forgotten. It also means that release notes can go through the same review |
9 |
process used for managing code and other documentation changes. |
10 |
|
11 |
Reno stores each release note in a separate file to enable a large number of |
12 |
developers to work on multiple patches simultaneously, all targeting the same |
13 |
branch, without worrying about merge conflicts. This cuts down on the need to |
14 |
rebase or otherwise manually resolve conflicts, and keeps a development team |
15 |
moving quickly. |
16 |
|
17 |
Reno also supports multiple branches, allowing release notes to be back-ported |
18 |
from master to maintenance branches together with the code for bug fixes. |
19 |
|
20 |
WWW: https://docs.openstack.org/reno/ |