]>
Commit | Line | Data |
---|---|---|
11fdf7f2 TL |
1 | ============= |
2 | Ceph Releases | |
3 | ============= | |
4 | ||
5 | Current | |
6 | ------- | |
7 | ||
8 | .. ceph_releases:: releases.yml | |
9 | ||
10 | Timeline | |
11 | -------- | |
12 | ||
13 | .. ceph_timeline:: releases.yml development mimic luminous kraken jewel infernalis hammer giant firefly emperor dumpling | |
14 | ||
15 | .. _Mimic: ../mimic | |
16 | .. _13.2.4: ../mimic#v13-2-4-mimic | |
17 | .. _13.2.3: ../mimic#v13-2-3-mimic | |
18 | .. _13.2.2: ../mimic#v13-2-2-mimic | |
19 | .. _13.2.1: ../mimic#v13-2-1-mimic | |
20 | .. _13.2.0: ../mimic#v13-2-0-mimic | |
21 | ||
22 | .. _Luminous: ../luminous#v12-2-0-luminous | |
23 | .. _12.2.10: ../luminous#v12-2-10-luminous | |
24 | .. _12.2.9: ../luminous#v12-2-9-luminous | |
25 | .. _12.2.8: ../luminous#v12-2-8-luminous | |
26 | .. _12.2.7: ../luminous#v12-2-7-luminous | |
27 | .. _12.2.6: ../luminous#v12-2-6-luminous | |
28 | .. _12.2.5: ../luminous#v12-2-5-luminous | |
29 | .. _12.2.4: ../luminous#v12-2-4-luminous | |
30 | .. _12.2.3: ../luminous#v12-2-3-luminous | |
31 | .. _12.2.2: ../luminous#v12-2-2-luminous | |
32 | .. _12.2.1: ../luminous#v12-2-1-luminous | |
33 | .. _12.2.0: ../luminous#v12-2-0-luminous | |
34 | ||
35 | .. _11.2.1: ../kraken#v11-2-1-kraken | |
36 | .. _11.2.0: ../kraken#v11-2-0-kraken | |
37 | .. _Kraken: ../kraken#v11-2-0-kraken | |
38 | ||
39 | .. _11.0.2: ../kraken#v11-0-2-kraken | |
40 | ||
41 | .. _10.2.11: ../jewel#v10-2-11-jewel | |
42 | .. _10.2.10: ../jewel#v10-2-10-jewel | |
43 | .. _10.2.9: ../jewel#v10-2-9-jewel | |
44 | .. _10.2.8: ../jewel#v10-2-8-jewel | |
45 | .. _10.2.7: ../jewel#v10-2-7-jewel | |
46 | .. _10.2.6: ../jewel#v10-2-6-jewel | |
47 | .. _10.2.5: ../jewel#v10-2-5-jewel | |
48 | .. _10.2.4: ../jewel#v10-2-4-jewel | |
49 | .. _10.2.3: ../jewel#v10-2-3-jewel | |
50 | .. _10.2.2: ../jewel#v10-2-2-jewel | |
51 | .. _10.2.1: ../jewel#v10-2-1-jewel | |
52 | .. _10.2.0: ../jewel#v10-2-0-jewel | |
53 | .. _Jewel: ../jewel#v10-2-0-jewel | |
54 | ||
55 | .. _10.1.2: ../jewel#v10-1-2-jewel-release-candidate | |
56 | .. _10.1.1: ../jewel#v10-1-1-jewel-release-candidate | |
57 | .. _10.1.0: ../jewel#v10-1-0-jewel-release-candidate | |
58 | .. _10.0.5: ../jewel#v10-0-5 | |
59 | .. _10.0.3: ../jewel#v10-0-3 | |
60 | .. _10.0.2: ../jewel#v10-0-2 | |
61 | .. _10.0.1: ../jewel#v10-0-1 | |
62 | .. _10.0.0: ../jewel#v10-0-0 | |
63 | ||
64 | .. _9.2.1: ../infernalis#v9-2-1-infernalis | |
65 | .. _9.2.0: ../infernalis#v9-2-0-infernalis | |
66 | .. _Infernalis: ../infernalis#v9-2-0-infernalis | |
67 | ||
68 | .. _9.1.0: ../infernalis#v9-1-0 | |
69 | .. _9.0.3: ../infernalis#v9-0-3 | |
70 | .. _9.0.2: ../infernalis#v9-0-2 | |
71 | .. _9.0.1: ../infernalis#v9-0-1 | |
72 | .. _9.0.0: ../infernalis#v9-0-0 | |
73 | ||
74 | .. _0.94.10: ../hammer#v0-94-10-hammer | |
75 | .. _0.94.9: ../hammer#v0-94-9-hammer | |
76 | .. _0.94.8: ../hammer#v0-94-8-hammer | |
77 | .. _0.94.7: ../hammer#v0-94-7-hammer | |
78 | .. _0.94.6: ../hammer#v0-94-6-hammer | |
79 | .. _0.94.5: ../hammer#v0-94-5-hammer | |
80 | .. _0.94.4: ../hammer#v0-94-4-hammer | |
81 | .. _0.94.3: ../hammer#v0-94-3-hammer | |
82 | .. _0.94.2: ../hammer#v0-94-2-hammer | |
83 | .. _0.94.1: ../hammer#v0-94-1-hammer | |
84 | .. _0.94: ../hammer#v0-94-hammer | |
85 | .. _Hammer: ../hammer#v0-94-hammer | |
86 | ||
87 | .. _0.93: ../hammer#v0-93 | |
88 | .. _0.92: ../hammer#v0-92 | |
89 | .. _0.91: ../hammer#v0-91 | |
90 | .. _0.90: ../hammer#v0-90 | |
91 | .. _0.89: ../hammer#v0-89 | |
92 | .. _0.88: ../hammer#v0-88 | |
93 | ||
94 | .. _0.87.2: ../giant#v0-87-2-giant | |
95 | .. _0.87.1: ../giant#v0-87-1-giant | |
96 | .. _0.87: ../giant#v0-87-giant | |
97 | .. _Giant: ../giant#v0-87-giant | |
98 | ||
99 | .. _0.86: ../giant#v0-86 | |
100 | .. _0.85: ../giant#v0-85 | |
101 | .. _0.84: ../giant#v0-84 | |
102 | .. _0.83: ../giant#v0-83 | |
103 | .. _0.82: ../giant#v0-82 | |
104 | .. _0.81: ../giant#v0-81 | |
105 | ||
106 | .. _0.80.11: ../firefly#v0-80-11-firefly | |
107 | .. _0.80.10: ../firefly#v0-80-10-firefly | |
108 | .. _0.80.9: ../firefly#v0-80-9-firefly | |
109 | .. _0.80.8: ../firefly#v0-80-8-firefly | |
110 | .. _0.80.7: ../firefly#v0-80-7-firefly | |
111 | .. _0.80.6: ../firefly#v0-80-6-firefly | |
112 | .. _0.80.5: ../firefly#v0-80-5-firefly | |
113 | .. _0.80.4: ../firefly#v0-80-4-firefly | |
114 | .. _0.80.3: ../firefly#v0-80-3-firefly | |
115 | .. _0.80.2: ../firefly#v0-80-2-firefly | |
116 | .. _0.80.1: ../firefly#v0-80-1-firefly | |
117 | .. _0.80: ../firefly#v0-80-firefly | |
118 | .. _Firefly: ../firefly#v0-80-firefly | |
119 | ||
120 | .. _0.79: ../firefly#v0-79 | |
121 | .. _0.78: ../firefly#v0-78 | |
122 | .. _0.77: ../firefly#v0-77 | |
123 | .. _0.76: ../firefly#v0-76 | |
124 | .. _0.75: ../firefly#v0-75 | |
125 | .. _0.74: ../firefly#v0-74 | |
126 | .. _0.73: ../firefly#v0-73 | |
127 | ||
128 | .. _0.72.2: ../emperor#v0-72-2-emperor | |
129 | .. _0.72.1: ../emperor#v0-72-1-emperor | |
130 | .. _0.72: ../emperor#v0-72-emperor | |
131 | .. _Emperor: ../emperor#v0-72-emperor | |
132 | ||
133 | .. _0.71: ../dumpling#v0-71 | |
134 | .. _0.70: ../dumpling#v0-70 | |
135 | .. _0.69: ../dumpling#v0-69 | |
136 | .. _0.68: ../dumpling#v0-68 | |
137 | ||
138 | .. _0.67.11: ../dumpling#v0-67-11-dumpling | |
139 | .. _0.67.10: ../dumpling#v0-67-10-dumpling | |
140 | .. _0.67.9: ../dumpling#v0-67-9-dumpling | |
141 | .. _0.67.8: ../dumpling#v0-67-8-dumpling | |
142 | .. _0.67.7: ../dumpling#v0-67-7-dumpling | |
143 | .. _0.67.6: ../dumpling#v0-67-6-dumpling | |
144 | .. _0.67.5: ../dumpling#v0-67-5-dumpling | |
145 | .. _0.67.4: ../dumpling#v0-67-4-dumpling | |
146 | .. _0.67.3: ../dumpling#v0-67-3-dumpling | |
147 | .. _0.67.2: ../dumpling#v0-67-2-dumpling | |
148 | .. _0.67.1: ../dumpling#v0-67-1-dumpling | |
149 | .. _0.67: ../dumpling#v0-67-dumpling | |
150 | .. _Dumpling: ../dumpling#v0-67-dumpling | |
151 | ||
152 | Understanding the release cycle | |
153 | ------------------------------- | |
154 | ||
155 | There is a new stable release cycle every nine (9) months, starting | |
156 | after the Luminous release (12.2.0). Each stable release series will | |
157 | receive a name (e.g., 'Mimic') and a major release number (e.g., 13 | |
158 | for Mimic because 'M' is the 13th letter of the alphabet). | |
159 | ||
160 | Releases are named after a species of cephalopod (usually the common | |
161 | name, since the latin names are harder to remember or pronounce). | |
162 | ||
163 | Version numbers have three components, *x.y.z*. *x* identifies the release | |
164 | cycle (e.g., 13 for Mimic). *y* identifies the release type: | |
165 | ||
166 | * x.0.z - development releases (for early testers and the brave at heart) | |
167 | * x.1.z - release candidates (for test clusters, brave users) | |
168 | * x.2.z - stable/bugfix releases (for users) | |
169 | ||
170 | This versioning convention started with the 9.y.z Infernalis cycle. Prior to | |
171 | that, versions looked with 0.y for development releases and 0.y.z for stable | |
172 | series. | |
173 | ||
174 | Development releases (x.0.z) | |
175 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
176 | ||
177 | Each development release (x.0.z) freezes the master development branch | |
178 | and applies `integration and upgrade tests | |
179 | <https://github.com/ceph/ceph/tree/master/qa/suites/>`_ before it is released. Once | |
180 | released, there is no effort to backport fixes; developer focus is on | |
181 | the next development release which is usually only a few weeks away. | |
182 | ||
183 | * Development release every 4 to 8 weeks | |
184 | * Intended for testing, not production deployments | |
185 | * Full integration testing | |
186 | * Upgrade testing from the last stable release(s) | |
187 | * Every effort is made to allow *offline* upgrades from previous | |
188 | development releases (meaning you can stop all daemons, upgrade, and | |
189 | restart). No attempt is made to support online rolling upgrades | |
190 | between development releases. This facilitates deployment of | |
191 | development releases on non-production test clusters without | |
192 | repopulating them with data. | |
193 | ||
194 | Release candidates (x.1.z) | |
195 | ^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
196 | ||
197 | There is a feature release roughly six (6) weeks prior to the planned | |
198 | initial stable release, after which focus shifts to stabilization and | |
199 | bug fixes only. | |
200 | ||
201 | * Release candidate release every 1-2 weeks | |
202 | * Intended for final testing and validation of the upcoming stable release | |
203 | ||
204 | Stable releases (x.2.z) | |
205 | ^^^^^^^^^^^^^^^^^^^^^^^ | |
206 | ||
207 | Once the initial stable release is made (x.2.0), there are | |
208 | semi-regular bug-fix point releases with bug fixes and (occasionally) | |
209 | small feature backports. Bug fixes are accumulated and included in | |
210 | the next point release. | |
211 | ||
212 | * Stable point release every 4 to 6 weeks | |
213 | * Intended for production deployments | |
214 | * Bug fix backports for two full release cycles. | |
215 | * Online, rolling upgrade support and testing from the last two (2) | |
216 | stable release(s) (starting from Luminous). | |
217 | * Online, rolling upgrade support and testing from prior stable point | |
218 | releases | |
219 | ||
220 | For each stable release: | |
221 | ||
222 | * `Integration and upgrade tests | |
223 | <https://github.com/ceph/ceph/tree/master/qa/suites/>`_ are run on a regular basis | |
224 | and `their results <http://pulpito.ceph.com/>`_ analyzed by Ceph | |
225 | developers. | |
226 | * `Issues <http://tracker.ceph.com/projects/ceph/issues?query_id=27>`_ | |
227 | fixed in the development branch (master) are scheduled to be backported. | |
228 | * When an issue found in the stable release is `reported | |
229 | <http://tracker.ceph.com/projects/ceph/issues/new>`_, it is | |
230 | triaged by Ceph developers. | |
231 | * The `stable releases and backport team <http://tracker.ceph.com/projects/ceph-releases/wiki>`_ | |
232 | publishes ``point releases`` including fixes that have been backported to the stable release. | |
233 | ||
234 | In the timeline above, the life time of a stable release series is | |
235 | calculated to be approximately 18 months (i.e., two 9 month release | |
236 | cycles) after the month of the first release. For example, Luminous | |
237 | (12.2.z) will reach end of life (EOL) shortly after Nautilus (14.2.0) is | |
238 | released. The lifetime of a release may vary because it depends on how | |
239 | quickly the stable releases are published. | |
240 | ||
241 | The life time for Jewel and Kraken are slightly different. Prior to | |
242 | Luminous, only every other stable release was an "LTS" release. | |
243 | Therefore, | |
244 | ||
245 | * Upgrades are supported from Jewel -> Kraken -> Luminous and Jewel -> Luminous. | |
246 | * Upgrades from Jewel or Kraken must upgrade to Luminous first before proceeding further (e.g., Kraken -> Luminous -> Mimic but not Kraken -> Mimic). | |
247 | * Jewel will be maintained until Mimic is released in the spring of 2018. | |
248 | * Kraken is no longer maintained. |