openstack/horizon
Code Issues Proposed changes
horizon/doc/source/contributor/policy.rst
Akihiro Motoki 882b5f0582 Assume features from N-4 release instead of N-3 
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
2019-10-15 15:11:47 +09:00

1.6 KiB
Raw Blame History

Project policies

This page collects basic policies on horizon development.

Back-end service support

  • N release of horizon supports N and N-1 releases of back-end OpenStack services (like nova, cinder, neutron and so on). This allows operators to upgrade horizon separately from other OpenStack services.
  • Horizon should check features in back-end services through APIs as much as 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-4 releases (which means the recent four releases including the development version) are assumed without checking the availability of features to simplify the implementation.
  • Removals and deprecations of back-end feature supports basically follows the standard deprecation policy defined by the technical committee, but there are some notes. Deprecations in back-end services are applied to corresponding horizon features automatically and it is allowed to drop some feature from horizon without an explicit deprecation.

Django support

  • Horizon usually syncs with Django's Roadmap and supports LTS (long term support) versions of Django as of the feature freeze of each OpenStack release. Supports for other maintained Django versions are optional and best-effort.