Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc/releases: update release cycle docs #18117

Merged
merged 2 commits into from Oct 6, 2017

Conversation

@liewegas
Copy link
Member

commented Oct 4, 2017

Signed-off-by: Sage Weil sage@redhat.com

@liewegas liewegas requested review from theanalyst, jdurgin, jecluis, jcsp and dillaman Oct 4, 2017

@liewegas liewegas force-pushed the liewegas:wip-lts branch 2 times, most recently from a988889 to cbaefde Oct 4, 2017

@dillaman
Copy link
Contributor

left a comment

The definition of LTS was dropped but it's still used in the release timeline at the top of the document. Given the new definition of "stable", one would think that Kraken should still be supported.

@liewegas liewegas force-pushed the liewegas:wip-lts branch from cbaefde to cbed793 Oct 4, 2017

@liewegas

This comment has been minimized.

Copy link
Member Author

commented Oct 4, 2017

Updated:

  • removed LTS vs Stable from chart
  • added EOL in its place for retired releases
  • added paragraph about Jewel and Kraken diverging from the (new) pattern
@ceph-jenkins

This comment has been minimized.

Copy link
Collaborator

commented Oct 4, 2017

OK - docs built

@@ -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 |

This comment has been minimized.

Copy link
@amitkumar50

amitkumar50 Oct 5, 2017

Contributor

tabs left


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

This comment has been minimized.

Copy link
@amitkumar50

amitkumar50 Oct 5, 2017

Contributor

extra _ after >


The life time for Jewel and Kraken are slightly different. Prior to
Luminous, only every other stable release was an "LTS" release.
Therefore,

This comment has been minimized.

Copy link
@amitkumar50

amitkumar50 Oct 5, 2017

Contributor

why gap in therefore? and commencing line

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.

This comment has been minimized.

Copy link
@singler

singler Oct 5, 2017

Contributor

Maybe we should use "Mimic" examples in section as this is new policy which wasn't present when Jewel was current?

* 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

This comment has been minimized.

Copy link
@theanalyst

theanalyst Oct 5, 2017

Member

Should we mention that this applies only after L, from Luminous release of ceph,

small feature backports. Bug fixes are accumulated and included in
the next point release.

* Stable point release every 3 to 6 weeks

This comment has been minimized.

Copy link
@theanalyst

theanalyst Oct 5, 2017

Member

more realistically 4-6 weeks?

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

This comment has been minimized.

Copy link
@smithfarm

smithfarm Oct 5, 2017

Contributor

s/depend/depends/

* 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

This comment has been minimized.

Copy link
@smithfarm

smithfarm Oct 5, 2017

Contributor

Release numbering conventions

@liewegas liewegas force-pushed the liewegas:wip-lts branch from cbed793 to 9767f7f Oct 5, 2017

@liewegas

This comment has been minimized.

Copy link
Member Author

commented Oct 5, 2017

Moved the versioning scheme description earlier so the subsequent sections make sense.

@liewegas liewegas force-pushed the liewegas:wip-lts branch from 9767f7f to bab8b6d Oct 5, 2017

@liewegas

This comment has been minimized.

Copy link
Member Author

commented Oct 5, 2017

@theanalyst How does this look to you?

@liewegas liewegas requested a review from gregsfortytwo Oct 5, 2017

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

This comment has been minimized.

Copy link
@theanalyst

theanalyst Oct 6, 2017

Member

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

doc/releases: update release cycle docs
Signed-off-by: Sage Weil <sage@redhat.com>

@liewegas liewegas force-pushed the liewegas:wip-lts branch from bab8b6d to 158cc11 Oct 6, 2017

@liewegas liewegas merged commit 1ebb466 into ceph:master Oct 6, 2017

2 of 5 checks passed

Docs: build check Docs: failed with errors
Details
make check running make check
Details
make check (arm64) running make check
Details
Signed-off-by all commits in this PR are signed
Details
Unmodified Submodules submodules for project are unmodified
Details

@liewegas liewegas deleted the liewegas:wip-lts branch Oct 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.