openstack/python-openstackclient
Code Issues Proposed changes
4e6f47e28e
python-openstackclient/releasenotes/source/index.rst

43 lines
1.0 KiB
ReStructuredText
Raw Normal View History

Add reno for release notes management Change-Id: Iaaf3f9ca7cb431e41adfb2a052e01e2240a63a07
2015-12-02 10:04:39 -06:00
=============================
OpenStackClient Release Notes
=============================
.. toctree::
:maxdepth: 1
unreleased
Update reno for stable/rocky Change-Id: Ieb4130d9f9d420fb3b858b6972a1f2a896fa7fc4
2018-07-26 08:58:10 +00:00
rocky
Update reno for stable/queens Change-Id: Iace9272b22ec8ccc8790e63c3f5e435d497c5e71
2018-01-25 13:46:13 +00:00
queens
Update reno for stable/pike Change-Id: Ieea72b22a55b29283705e957a973a46f2e6c5848
2017-08-10 19:31:07 +00:00
pike
Update reno for stable/ocata Change-Id: I91d3a23f5e449efbfe350ad633135b4d725fbbe6
2017-01-31 23:36:54 +00:00
ocata
standardize release note page ordering In order to support automatically updating the release notes when we create stable branches, we want the pages to be in a standard order. This patch updates the order to be reverse chronological, so the most recent notes appear at the top. Change-Id: Ib364dcc8eb31275a31c83b68d7914263b183e393 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2016-09-07 17:08:46 -04:00
newton
Add mitaka release notes to master Change-Id: I00b3abe0ac8765989a83e491f1dc53db22283bdd
2017-02-01 14:25:07 -06:00
mitaka
Set up 3.x release notes Give the 2.x series its own release notes page, put the 3.x notes into the 'current' series page. This removes the OpenStack development cycle name from the release notes. We follow the intermediary release model, however the association with the common cycle release is something that we do not need to reflect in the doc structure. We want users to use the current version even with older clouds, not to think they need to use a 'Mitaka' OSC with a Mitaka cloud. Change-Id: Idbb6844824d50e5cd0fa64871b5aa625d4d237af
2016-06-04 11:09:52 -05:00
20_releases
Fix release note links to (now) external docs Moving the old release notes into the Reno releasenots tree broke the embedded :doc: roles. Restore these using sphinx.ext.extlinks to manage the URL to the OSC docs. Add the following aliases: * lpbug - generic Launchpad bug :lpbug:`123456` * oscbp - OSC blueprints :oscbp:`Blue Print <bp-name>` * oscdoc - OSC Docs :oscdoc:`Comamnd List <command-list>` Change-Id: Iecfdd666d961c35f0ccb3b9f10df1d2620cb099f
2016-06-03 16:56:55 -05:00
pre_20_releases
Set up 3.x release notes Give the 2.x series its own release notes page, put the 3.x notes into the 'current' series page. This removes the OpenStack development cycle name from the release notes. We follow the intermediary release model, however the association with the common cycle release is something that we do not need to reflect in the doc structure. We want users to use the current version even with older clouds, not to think they need to use a 'Mitaka' OSC with a Mitaka cloud. Change-Id: Idbb6844824d50e5cd0fa64871b5aa625d4d237af
2016-06-04 11:09:52 -05:00
OpenStack Releases
------------------
OpenStackClient is compatible with all currently supported OpenStack releases,
it does not require maintaining a 'Mitaka' version to match to a Mitala-release
cloud. The OpenStackClient release that was current when the corresponding
OpenStack release was made is shown below:
================= =======================
OpenStack Release OpenStackClient Release
================= =======================
Update release/stable branch table in docs Change-Id: I0d18be4f2ed14137010693f41526a261a0acca3b
2017-08-10 16:37:09 -05:00
Pike 3.12.0
mention the final ocata osc version in releasenotes we neglected to add the final osc version in our release note page, it should be 3.8.1 Change-Id: I4291a09924ce8beb29c8c3aff18962a43f0241b0
2017-02-02 21:30:52 -05:00
Ocata 3.8.1
More 3.3.0 release notes Plus minor doc formatting updates Change-Id: I849794e954cdeb582f7a0b104c62ec6688ead628
2016-10-07 14:52:34 -05:00
Newton 3.2.0
Set up 3.x release notes Give the 2.x series its own release notes page, put the 3.x notes into the 'current' series page. This removes the OpenStack development cycle name from the release notes. We follow the intermediary release model, however the association with the common cycle release is something that we do not need to reflect in the doc structure. We want users to use the current version even with older clouds, not to think they need to use a 'Mitaka' OSC with a Mitaka cloud. Change-Id: Idbb6844824d50e5cd0fa64871b5aa625d4d237af
2016-06-04 11:09:52 -05:00
Mitaka 2.3.0
Liberty 1.7.3
Kilo 1.0.6
Juno 0.4.1
Icehouse 0.3.1
================= =======================
Further details for historical OpenStack releases are found at the
`OpenStack Releases`_ page.
.. _`OpenStack Releases`: http://releases.openstack.org/
Copy Permalink