openstack/releases
Code Issues Proposed changes

add a few more details to the readme

Browse Source 
Explicitly say that every new release needs a new version number.

Include freeze weeks as a reason a release might be postponed.

Change-Id: Id417783a3e70977251ccba68253c3521f8959af7
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann
2016-10-05 12:31:55 -04:00
parent a09a061a40
commit 0ea69d559a
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.rst
View File

@@ -32,6 +32,10 @@ repository.
* Always add the new release to the end of the file being edited. The * Always add the new release to the end of the file being edited. The
version numbers will be reordered for display. version numbers will be reordered for display.
* Always pick new version numbers for new releases. We do not update
the contents of previously tagged releases, because that confuses
users who have already downloaded those packages.
* Set the first line (summary) of the commit message to the package * Set the first line (summary) of the commit message to the package
name and version being requested. name and version being requested.
@@ -117,8 +121,8 @@ team should +1 the following types of changes before they are approved.
Release Approval Release Approval
================ ================
Releases will only be denied during periods where there are known gate Releases will only be denied during freeze weeks, periods where there
issues, or when releasing will introduce unwanted are known gate issues, or when releasing will introduce unwanted
instability. Releases made late in a week may be delayed until early instability. Releases made late in a week may be delayed until early
in the next week unless there is a pressing need such as a gate in the next week unless there is a pressing need such as a gate
failure or security issue. failure or security issue.