openstack
/
requirements
Code Issues Proposed changes

Move the Stable rules under review guidlines 

Havign the stable rules in the middle of the tools section makes them
hard to find.  Move them to the Review guidelines.

Change-Id: I821cc6c311201cce80a260bc698f60171a2ee2e5
This commit is contained in:
Tony Breeds 2017-06-29 11:12:53 +10:00
parent 2086838ec6
commit 80a3d1bb71
1 changed files with 31 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

62
README.rst
View File

@ -157,37 +157,6 @@ Entries in all requirements files will have their versions updated to match
the entries listed in the global requirements. Excess entries will cause
errors in hard mode (the default) or be ignored in soft mode.
stable-branch maintenance
-------------------------
Upper-constraints
+++++++++++++++++
Most of the work is done by stable-maint in the releases project. The releases
project ensures valid stable releases (little to no API level changes, bugfix
only, etc). Once released, the new version is requested to be updated in
requirements. The following restrictions are in place to help ensure stable
branches do not break.
- In stable branches, we usually only update constraints for projects managed
within the OpenStack community. Exceptions are made for other projects when
there are gate issues. Those updates must be proposed by hand.
- The requirements team also verifies the new version's requirements changes
line up with the requirements in the stable branch (GR and UC).
Global-requirements
+++++++++++++++++++
These should be few and far between on stable branches, mainly masking known
bad versions or in extreme adding a maximum version allowable for a package.
We work to remove these caps as well.
New requirements
++++++++++++++++
In nearly all cases this is not allowed.
generate-constraints
--------------------
@ -431,6 +400,37 @@ changed when a ``global-requirements.txt`` change is proposed. In this case, ign
the changes to ``upper-constraints.txt`` and review the
``global-requirements.txt`` component of the change.
stable-branch maintenance
-------------------------
Upper-constraints
+++++++++++++++++
Most of the work is done by stable-maint in the releases project. The releases
project ensures valid stable releases (little to no API level changes, bugfix
only, etc). Once released, the new version is requested to be updated in
requirements. The following restrictions are in place to help ensure stable
branches do not break.
- In stable branches, we usually only update constraints for projects managed
within the OpenStack community. Exceptions are made for other projects when
there are gate issues. Those updates must be proposed by hand.
- The requirements team also verifies the new version's requirements changes
line up with the requirements in the stable branch (GR and UC).
Global-requirements
+++++++++++++++++++
These should be few and far between on stable branches, mainly masking known
bad versions or in extreme adding a maximum version allowable for a package.
We work to remove these caps as well.
New requirements
++++++++++++++++
In nearly all cases this is not allowed.
Resources
=========