openstack
/
ossa
Code Issues Proposed changes

Update AFFECTED_VERSIONS examples 

Change-Id: I6d9f87535ab86e4d79045496c468774cfa34c67a
This commit is contained in:
Tristan Cacqueray 2016-06-03 09:56:46 -04:00 committed by Jeremy Stanley
parent 5737ac5e3e
commit c6fb8a5601
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/source/vmt-process.rst
View File

@ -323,25 +323,26 @@ Impact Description ($DESCRIPTION)
By doing [action] a [actor] may [impact] resulting in [consequence].
Only [project deployment mode] are affected.
The AFFECTED_VERSIONS should read like this, while both Kilo and
Liberty still will have stable releases:
The AFFECTED_VERSIONS needs to stay valid after the fix is released.
For example, when kilo, liberty and mitaka are still security supported,
the AFFECTED_VERSIONS of keystone should read like this:
::
Affects: >=2015.1.0 <=2015.1.3, >=12.0.0 <=12.0.3
Affects: >=2015.1.0 <=2015.1.4, >=8.0.0 <=8.1.0 and ==9.0.0
Once the last Kilo point release is released, that line becomes:
Once kilo reaches end of life, that line becomes:
::
Affects: >=12.0.0 <=12.0.3
Affects: >=8.0.0 <=8.1.0 and ==9.0.0
If the oldest version affected is not easily identified, leave it
open-ended:
::
Affects: <=2015.1.3
Affects: <=8.1.0 and ==9.0.0
CVE Request Email (Private Issues)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^