summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFrank Kloeker <f.kloeker@telekom.de>2018-10-26 17:32:23 +0200
committerFrank Kloeker <f.kloeker@telekom.de>2018-10-26 17:32:23 +0200
commit97540206b940dc469aa4a0dc07591a69176cffd8 (patch)
tree312fe9ed199107d0e5312e0d253fdc5e1b6a7cad
parentfb6fc0df5bbb7a850abdd4f462d78edd60cd204e (diff)
Update information about releases
- remove unmaintained stuff and point to official release page - update information about Design Summit and PTG Change-Id: I7b503fba9bc9894b980d80788aea4414e369ad0c
Notes
Notes (review): Code-Review+2: Sean McGinnis <sean.mcginnis@gmail.com> Code-Review+2: Andreas Jaeger <jaegerandi@gmail.com> Workflow+1: Andreas Jaeger <jaegerandi@gmail.com> Verified+2: Zuul Submitted-by: Zuul Submitted-at: Fri, 02 Nov 2018 15:16:59 +0000 Reviewed-on: https://review.openstack.org/613619 Project: openstack/operations-guide Branch: refs/heads/master
-rw-r--r--doc/source/app-roadmaps.rst170
1 files changed, 12 insertions, 158 deletions
diff --git a/doc/source/app-roadmaps.rst b/doc/source/app-roadmaps.rst
index 48d28e5..0b4f2ef 100644
--- a/doc/source/app-roadmaps.rst
+++ b/doc/source/app-roadmaps.rst
@@ -10,15 +10,15 @@ up in the next release and perhaps further afield.
10 10
11OpenStack follows a six month release cycle, typically releasing in 11OpenStack follows a six month release cycle, typically releasing in
12April/May and October/November each year. At the start of each cycle, 12April/May and October/November each year. At the start of each cycle,
13the community gathers in a single location for a design summit. At the 13the community gathers in a single location for a Project Teams
14summit, the features for the coming releases are discussed, prioritized, 14Gathering (PTG). At the PTG, the features for the coming releases are
15and planned. The below figure shows an example release cycle, with dates 15discussed, prioritized, and planned. The below figure shows an example
16showing milestone releases, code freeze, and string freeze dates, along 16release cycle, with dates showing milestone releases, code freeze, and
17with an example of when the summit occurs. Milestones are interim releases 17string freeze dates, along with an example of when the summit occurs.
18within the cycle that are available as packages for download and 18Milestones are interim releases within the cycle that are available as
19testing. Code freeze is putting a stop to adding new features to the 19packages for download and testing. Code freeze is putting a stop to
20release. String freeze is putting a stop to changing any strings within 20adding new features to the release. String freeze is putting a stop to
21the source code. 21changing any strings within the source code.
22 22
23.. image:: figures/osog_ac01.png 23.. image:: figures/osog_ac01.png
24 :width: 100% 24 :width: 100%
@@ -30,154 +30,8 @@ Information Available to You
30There are several good sources of information available that you can use 30There are several good sources of information available that you can use
31to track your OpenStack development desires. 31to track your OpenStack development desires.
32 32
33Release notes are maintained on the OpenStack wiki, and also shown here: 33- `List of OpenStack releases and release
34 34 notes <https://releases.openstack.org/>`_
35.. list-table::
36 :widths: 25 25 25 25
37 :header-rows: 1
38
39 * - Series
40 - Status
41 - Releases
42 - Date
43 * - Liberty
44 - `Under Development
45 <https://wiki.openstack.org/wiki/Liberty_Release_Schedule>`_
46 - 2015.2
47 - Oct, 2015
48 * - Kilo
49 - `Current stable release, security-supported
50 <https://wiki.openstack.org/wiki/Kilo_Release_Schedule>`_
51 - `2015.1 <https://wiki.openstack.org/wiki/ReleaseNotes/Kilo>`_
52 - Apr 30, 2015
53 * - Juno
54 - `Security-supported
55 <https://wiki.openstack.org/wiki/Juno_Release_Schedule>`_
56 - `2014.2 <https://wiki.openstack.org/wiki/ReleaseNotes/Juno>`_
57 - Oct 16, 2014
58 * - Icehouse
59 - `End-of-life
60 <https://wiki.openstack.org/wiki/Icehouse_Release_Schedule>`_
61 - `2014.1 <https://wiki.openstack.org/wiki/ReleaseNotes/Icehouse>`_
62 - Apr 17, 2014
63 * -
64 -
65 - `2014.1.1 <https://wiki.openstack.org/wiki/ReleaseNotes/2014.1.1>`_
66 - Jun 9, 2014
67 * -
68 -
69 - `2014.1.2 <https://wiki.openstack.org/wiki/ReleaseNotes/2014.1.2>`_
70 - Aug 8, 2014
71 * -
72 -
73 - `2014.1.3 <https://wiki.openstack.org/wiki/ReleaseNotes/2014.1.3>`_
74 - Oct 2, 2014
75 * - Havana
76 - End-of-life
77 - `2013.2 <https://wiki.openstack.org/wiki/ReleaseNotes/Havana>`_
78 - Apr 4, 2013
79 * -
80 -
81 - `2013.2.1 <https://wiki.openstack.org/wiki/ReleaseNotes/2013.2.1>`_
82 - Dec 16, 2013
83 * -
84 -
85 - `2013.2.2 <https://wiki.openstack.org/wiki/ReleaseNotes/2013.2.2>`_
86 - Feb 13, 2014
87 * -
88 -
89 - `2013.2.3 <https://wiki.openstack.org/wiki/ReleaseNotes/2013.2.3>`_
90 - Apr 3, 2014
91 * -
92 -
93 - `2013.2.4 <https://wiki.openstack.org/wiki/ReleaseNotes/2013.2.4>`_
94 - Sep 22, 2014
95 * -
96 -
97 - `2013.2.1 <https://wiki.openstack.org/wiki/ReleaseNotes/2013.2.1>`_
98 - Dec 16, 2013
99 * - Grizzly
100 - End-of-life
101 - `2013.1 <https://wiki.openstack.org/wiki/ReleaseNotes/Grizzly>`_
102 - Apr 4, 2013
103 * -
104 -
105 - `2013.1.1 <https://wiki.openstack.org/wiki/ReleaseNotes/2013.1.1>`_
106 - May 9, 2013
107 * -
108 -
109 - `2013.1.2 <https://wiki.openstack.org/wiki/ReleaseNotes/2013.1.2>`_
110 - Jun 6, 2013
111 * -
112 -
113 - `2013.1.3 <https://wiki.openstack.org/wiki/ReleaseNotes/2013.1.3>`_
114 - Aug 8, 2013
115 * -
116 -
117 - `2013.1.4 <https://wiki.openstack.org/wiki/ReleaseNotes/2013.1.4>`_
118 - Oct 17, 2013
119 * -
120 -
121 - `2013.1.5 <https://wiki.openstack.org/wiki/ReleaseNotes/2013.1.5>`_
122 - Mar 20, 2015
123 * - Folsom
124 - End-of-life
125 - `2012.2 <https://wiki.openstack.org/wiki/ReleaseNotes/Folsom>`_
126 - Sep 27, 2012
127 * -
128 -
129 - `2012.2.1 <https://wiki.openstack.org/wiki/ReleaseNotes/2012.2.1>`_
130 - Nov 29, 2012
131 * -
132 -
133 - `2012.2.2 <https://wiki.openstack.org/wiki/ReleaseNotes/2012.2.2>`_
134 - Dec 13, 2012
135 * -
136 -
137 - `2012.2.3 <https://wiki.openstack.org/wiki/ReleaseNotes/2012.2.3>`_
138 - Jan 31, 2013
139 * -
140 -
141 - `2012.2.4 <https://wiki.openstack.org/wiki/ReleaseNotes/2012.2.4>`_
142 - Apr 11, 2013
143 * - Essex
144 - End-of-life
145 - `2012.1 <https://wiki.openstack.org/wiki/ReleaseNotes/Essex>`_
146 - Apr 5, 2012
147 * -
148 -
149 - `2012.1.1 <https://wiki.openstack.org/wiki/ReleaseNotes/2012.1.1>`_
150 - Jun 22, 2012
151 * -
152 -
153 - `2012.1.2 <https://wiki.openstack.org/wiki/ReleaseNotes/2012.1.2>`_
154 - Aug 10, 2012
155 * -
156 -
157 - `2012.1.3 <https://wiki.openstack.org/wiki/ReleaseNotes/2012.1.3>`_
158 - Oct 12, 2012
159 * - Diablo
160 - Deprecated
161 - `2011.3 <https://wiki.openstack.org/wiki/ReleaseNotes/Diablo>`_
162 - Sep 22, 2011
163 * -
164 -
165 - `2011.3.1 <https://wiki.openstack.org/wiki/ReleaseNotes/2011.3.1>`_
166 - Jan 19, 2012
167 * - Cactus
168 - Deprecated
169 - `2011.2 <https://wiki.openstack.org/wiki/ReleaseNotes/Cactus>`_
170 - Apr 15, 2011
171 * - Bexar
172 - Deprecated
173 - `2011.1 <https://wiki.openstack.org/wiki/ReleaseNotes/Bexar>`_
174 - Feb 3, 2011
175 * - Austin
176 - Deprecated
177 - `2010.1 <https://wiki.openstack.org/wiki/ReleaseNotes/Austin>`_
178 - Oct 21, 2010
179
180Here are some other resources:
181 35
182- `A breakdown of current features under development, with their target 36- `A breakdown of current features under development, with their target
183 milestone <https://status.openstack.org/release/>`_ 37 milestone <https://status.openstack.org/release/>`_
@@ -208,7 +62,7 @@ approved by project team members, and development can begin.
208 62
209Therefore, the fastest way to get your feature request up for 63Therefore, the fastest way to get your feature request up for
210consideration is to create an Etherpad with your ideas and propose a 64consideration is to create an Etherpad with your ideas and propose a
211session to the design summit. If the design summit has already passed, 65session to the PTG. If the PTG has already passed,
212you may also create a blueprint directly. Read this `blog post about how 66you may also create a blueprint directly. Read this `blog post about how
213to work with blueprints 67to work with blueprints
214<http://vmartinezdelacruz.com/how-to-work-with-blueprints-without-losing-your-mind/>`_ 68<http://vmartinezdelacruz.com/how-to-work-with-blueprints-without-losing-your-mind/>`_