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
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
Currently OSC release notes are in the OpenStack releasenote
site. There is a collection of old non-reno release notes in
our docs folder. Move the non-reno release notes to the
reno directionary.
Change-Id: Ie51fd1e1115d606e5d2739014d3720eedc8dc225
