<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/openstack/python-openstackclient.git/releasenotes/source/unreleased.rst, branch 3.16.1</title>
<subtitle>opendev.org: openstack/python-openstackclient
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/python-openstackclient.git/'/>
<entry>
<title>Update earliest-version number format in release notes</title>
<updated>2016-12-22T13:49:27+00:00</updated>
<author>
<name>Rodolfo Alonso Hernandez</name>
<email>rodolfo.alonso.hernandez@intel.com</email>
</author>
<published>2016-12-22T13:49:27+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=5084ce14b0b99cb79286d3dd57ebb7c5ea10ac1c'/>
<id>5084ce14b0b99cb79286d3dd57ebb7c5ea10ac1c</id>
<content type='text'>
Change-Id: I67deca8d2ff1f63d272b8d5b78cb31efd6e6d4df
Closes-Bug: #1652054
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Change-Id: I67deca8d2ff1f63d272b8d5b78cb31efd6e6d4df
Closes-Bug: #1652054
</pre>
</div>
</content>
</entry>
<entry>
<title>Set up 3.x release notes</title>
<updated>2016-06-07T22:34:38+00:00</updated>
<author>
<name>Dean Troyer</name>
<email>dtroyer@gmail.com</email>
</author>
<published>2016-06-04T16:09:52+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=b8730114b9a2f5519a0405a44c80f50367f2b5c0'/>
<id>b8730114b9a2f5519a0405a44c80f50367f2b5c0</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>Add reno for release notes management</title>
<updated>2015-12-02T20:32:07+00:00</updated>
<author>
<name>Dean Troyer</name>
<email>dtroyer@gmail.com</email>
</author>
<published>2015-12-02T16:04:39+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/python-openstackclient.git/commit/?id=afd1b489ff2137ef1ee0eef1ec1c202f2e1ac899'/>
<id>afd1b489ff2137ef1ee0eef1ec1c202f2e1ac899</id>
<content type='text'>
Change-Id: Iaaf3f9ca7cb431e41adfb2a052e01e2240a63a07
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Change-Id: Iaaf3f9ca7cb431e41adfb2a052e01e2240a63a07
</pre>
</div>
</content>
</entry>
</feed>
