openstack/releases
Code Issues Proposed changes

Allow multiple releses in cycle-automatic

Browse Source 
In some cases, teams want to push intermediary releases
for cycle-automatic deliverables. This should be OK, as
long as cycle-automatic is limited to specific deliverables.

Adjust language in the doc to match that.

Change-Id: I8bec726892de5d05a90fb7ac84bcf442c057f819
This commit is contained in:
Thierry Carrez
2019-08-02 11:36:17 +02:00
parent 8f0fc62593
commit ed0e471a3c
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/reference/release_models.rst
View File

@@ -123,9 +123,10 @@ cycle-automatic
===============
The "cycle-automatic" model is used by specific technical deliverables
that just need to be automatically released once (and only once) at the
end of a cycle. Those do not need a stable branch created. This may be
applied only to "tempest-plugin" or "other" deliverables.
that need to be automatically released once at the end of a cycle.
Those may, optionally, also be released in the middle of the cycle.
Those do not need a stable branch created. This may be applied only
to "tempest-plugin" or "other" deliverables.
* "cycle-automatic" deliverables will be automatically released by the
release team once at the end of a cycle, using the current HEAD of the