openstack/horizon
Code Issues Proposed changes
horizon/doc/source/contributor/policies/supported-software.rst
Akihiro Motoki c897a8e444 doc: Reorganize contributor doc 
Ussuri community goal "Project specific contributor and PTL docs"
want us to use doc/source/contributor/contributing.rst as an entry
point, but the current contributor/contributing.rst in horizon
contains a lot of information.

Before updating the file to satisfy the community goal criteria,
this commit reorganize the contributor doc.
It splits the existing contents in contributing.rst into pieces.

Change-Id: I8aa9a310a99e0eed5a93ed040a02a2829ee09bf7
2020-08-20 08:34:11 +09:00

1.5 KiB
Raw Blame History

Supported Software

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.