openstack/releases
Code Issues Proposed changes

add info about WIP release requests for RCs

Browse Source 
One aspect of the process that wasn't covered in the original draft was
the suggestion that teams that know they will have more than one release
candidate can submit the request as a WIP patch.

Change-Id: I6f7750f2975a71341f19aa1ef72c4f30effb920f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2016-08-01 16:26:58 -04:00
parent d542d6b3a6
commit 14d855cb8f
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
PROCESS.rst
View File

@ -144,7 +144,10 @@ Try to avoid creating more than 3 release candidates so we are not
creating candidates that consumers are then trained to ignore. Each
release candidate should be kept for at least 1 day, so if there is a
proposal to create RCX but clearly a reason to create another one,
delay RCX to include the additional patches.
delay RCX to include the additional patches. Teams that know they will
need additional release candidates can submit the requests and mark
them WIP until actually ready, so the release team knows that more
candidates are coming.
1. Encourage liaisons to merge all translation patches.