doc/releases: update release cycle docs #18117
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
liewegas
requested review from
theanalyst,
jdurgin,
jecluis,
jcsp and
dillaman
liewegas
force-pushed
the
wip-lts
branch
2 times, most recently
from
a988889
to
cbaefde
Compare
dillaman
reviewed
Oct 4, 2017
|
Updated:
|
|
OK - docs built |
amitkumar50
reviewed
Oct 5, 2017
| @@ -7,7 +7,7 @@ Timeline | |||
|
|
|||
| +----------------------+-------------+-----------+----------+---------------+-----------+----------+------------+------------+-------------+ | |||
| | | `Luminous`_ | `Kraken`_ | `Jewel`_ | `Infernalis`_ | `Hammer`_ | `Giant`_ | `Firefly`_ | `Emperor`_ | `Dumpling`_ | | |||
| | | LTS | Stable | LTS | Stable | LTS | Stable | LTS | Stable | LTS | | |||
| | | | EOL | | EOL | EOL | EOL | EOL | EOL | EOL | | |||
|
|
||
| Each development release (x.0.z) freezes the master development branch | ||
| and applies `integration and upgrade tests | ||
| <https://github.com/ceph/ceph-qa-suite>`_ before it is released. Once |
|
|
||
| The life time for Jewel and Kraken are slightly different. Prior to | ||
| Luminous, only every other stable release was an "LTS" release. | ||
| Therefore, |
There was a problem hiding this comment.
why gap in therefore? and commencing line
singler
reviewed
Oct 5, 2017
doc/releases.rst
Outdated
| stable release series will receive a name (e.g., 'Jewel') and a major | ||
| release number (e.g., 10 for Jewel because 'J' is the 10th letter of | ||
| the alphabet). Each release has a version like 10.y.z. | ||
|
|
There was a problem hiding this comment.
Maybe we should use "Mimic" examples in section as this is new policy which wasn't present when Jewel was current?
theanalyst
reviewed
Oct 5, 2017
doc/releases.rst
Outdated
| * Long Term Stable : until the next two LTS are published | ||
| * Stable release : until the next stable release is published | ||
| * Development / testing release : no backports | ||
| There is a new stable release cycle every nine (9) months. Each |
There was a problem hiding this comment.
Should we mention that this applies only after L, from Luminous release of ceph,
doc/releases.rst
Outdated
| small feature backports. Bug fixes are accumulated and included in | ||
| the next point release. | ||
|
|
||
| * Stable point release every 3 to 6 weeks |
There was a problem hiding this comment.
more realistically 4-6 weeks?
smithfarm
reviewed
Oct 5, 2017
doc/releases.rst
Outdated
| extended to May 2015. | ||
| In the timeline, the life time of a stable release series is | ||
| calculated to be approximately 18 months after the month of the first | ||
| release. The lifetime of a release may vary because it depend on how |
smithfarm
reviewed
Oct 5, 2017
doc/releases.rst
Outdated
| * Upgrades beyond Luminous must stop at Luminous. | ||
| * Jewel will be maintained until Mimic is released in the Spring of 2018. | ||
| * Kraken is no longer maintained. | ||
|
|
||
|
|
||
| Release numbers conventions |
There was a problem hiding this comment.
Release numbering conventions
|
Moved the versioning scheme description earlier so the subsequent sections make sense. |
Signed-off-by: Sage Weil <sage@redhat.com>
|
@theanalyst How does this look to you? |
theanalyst
reviewed
Oct 6, 2017
doc/releases.rst
Outdated
| Subsequent development releases will be 9.0.1, 9.0.2, etc. | ||
| In the timeline, the life time of a stable release series is | ||
| calculated to be approximately 18 months after the month of the first | ||
| release. The lifetime of a release may vary because it depends on how |
There was a problem hiding this comment.
Maybe mention that this is because, we maintain backport releases for 2 release cycles, ie, Luminous will be maintained until the first stable release of Nautilus
Signed-off-by: Sage Weil <sage@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Sage Weil sage@redhat.com