openstack/releases
Code Issues Proposed changes

Fix formatting issues in R-2 week

Browse Source 
Wrong indent resulted in formatting issues in the HTML rendering.

Change-Id: I325f42d64cb0d9f1b16d4f7957d975feeca3b897
This commit is contained in:
Thierry Carrez 2020-04-09 12:28:39 +02:00
parent f33c46d9e5
commit 0ada281623
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/source/reference/process.rst
View File

@ -1108,17 +1108,17 @@ R-2 week
and we can have divergence between the requirements being tested
and being declared as correct.
- Remind the QA PTL to create new branch specific jobs for our two
branchless projects, devstack-gate and tempest, in the tempest repo.
Configure tempest to run them on all changes, voting. Configure tempest
to run them as periodic bitrot jobs as well. All this can be done in one
tempest patch, for example, see https://review.opendev.org/521888.
Configure devstack-gate to run the new jobs in check pipeline only,
non-voting, for example see https://review.opendev.org/545144.
- Remind the QA PTL to create new branch specific jobs for our two
branchless projects, devstack-gate and tempest, in the tempest repo.
Configure tempest to run them on all changes, voting. Configure tempest
to run them as periodic bitrot jobs as well. All this can be done in one
tempest patch, for example, see https://review.opendev.org/521888.
Configure devstack-gate to run the new jobs in check pipeline only,
non-voting, for example see https://review.opendev.org/545144.
- Remind the QA PTL to add the new branch to the list of branches in the
periodic-stable job templates in openstack-zuul-jobs. For example, see
https://review.opendev.org/545268/.
- Remind the QA PTL to add the new branch to the list of branches in the
periodic-stable job templates in openstack-zuul-jobs. For example, see
https://review.opendev.org/545268/.
#. Ensure that all projects that are publishing release notes have the
notes link included in their deliverable file. See