| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Add mitaka release notes to master | Dean Troyer | 2017-02-01 | 1 | -0/+6 |
| | | | | | Change-Id: I00b3abe0ac8765989a83e491f1dc53db22283bdd | ||||
| * | Set up 3.x release notes | Dean Troyer | 2016-06-07 | 1 | -6/+0 |
| | | | | | | | | | | | | | | | 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 | ||||
| * | include old release notes in reno | Rui Chen | 2016-05-31 | 1 | -3/+3 |
| | | | | | | | | | | 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 | 1 | -0/+6 |
| Change-Id: I4737774ee596bd3cf64c5deed3132afb1add3bcf | |||||
 |
index : delta/openstack/python-openstackclient.git | |
| opendev.org: openstack/python-openstackclient |
| summaryrefslogtreecommitdiff |