openstack/horizon
Code Issues Proposed changes

Assume features from N-4 release instead of N-3

Browse Source 
Curretnly, features from N-3 release are assumed as a baseline
in the horizon development policy document.
LTS of Ubuntu Cloud Archive supports upgrade from N-4 to N.
If we assume a case where horizon is upgraded first, N release of
horizon needs to be able to run with N-4 release of back-end services.
The difference of N-3 and N-4 would be small, so it sounds reasonable
to assume features from N-4 release.

N-4 is chosen considering LTS support in the major OpenStack distributions:
* Red Hat OpenStack Platform (RHOSP): X -> X+3
  https://access.redhat.com/support/policy/updates/openstack/platform/
* SuSE OpenStack Cloud (SOC): X -> X+2
  https://www.suse.com/releasenotes/x86_64/SUSE-OPENSTACK-CLOUD/8/#Upgrade
* Ubuntu Cloud Archive: X -> X+4
  https://www.ubuntu.com/about/release-cycle

Change-Id: If7007e9d5b912b48d6bf3e4fac5decc53cd8388b
This commit is contained in:
Akihiro Motoki 2019-10-15 15:11:47 +09:00
parent 307e884eaa
commit 882b5f0582
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/contributor/policy.rst
View File

@ -16,7 +16,7 @@ Back-end service support
possible by using micro-versioning for nova, cinder and so on and API
extensions for neutron (and others if any).
* Related to the previous item, features available in ``N-3`` releases
* Related to the previous item, features available in ``N-4`` releases
(which means the recent four releases including the development version)
are assumed without checking the availability of features
to simplify the implementation.