delta/openstack/python-openstackclient.git - opendev.org: openstack/python-openstackclient

	Commit message (Collapse)	Author	Age	Files	Lines
*	Update the description of project in releasenotes.	qtang	2016-07-29	1	-1/+1
\| \| \| \|	Change-Id: I1fe0e52d2e049d34666a6d94bac1d85b91a78b19
*	Set up 3.x release notes	Dean Troyer	2016-06-07	4	-7/+31
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	Fix release note links to (now) external docs	Dean Troyer	2016-06-06	3	-14/+33
\| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	include old release notes in reno	Rui Chen	2016-05-31	3	-3/+699
\| \| \| \| \| \| \| \| \|	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
*	Update reno for stable/mitaka	Doug Hellmann	2016-03-10	2	-0/+7
\| \| \| \|	Change-Id: I4737774ee596bd3cf64c5deed3132afb1add3bcf
*	Add reno for release notes management	Dean Troyer	2015-12-02	5	-0/+295
	Change-Id: Iaaf3f9ca7cb431e41adfb2a052e01e2240a63a07