Skip to content

doc: remove "How is an LTS release cut?" section #26955

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.

Sign up for GitHub

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

Closed
Trott wants to merge 3 commits into from
Closed

doc: remove "How is an LTS release cut?" section #26955

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
53a2b97
doc: remove "How is an LTS release cut?" section
Trott Mar 28, 2019
bb7949d
fixup! doc: remove "How is an LTS release cut?" section
Trott Mar 28, 2019
64b0648
fixup! fixup! doc: remove "How is an LTS release cut?" section
Trott Mar 28, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
doc: remove "How is an LTS release cut?" section 
The release process is in the Release plan, linked earlier in the doc.
Don't include information here because duplicated information is likely
to drift apart, resulting in contradictions and a lack of clarity about
which document is correct. (I think the text removed is already
out-of-date. I could be wrong, and it doesn't much matter, as it should
be removed anyway.) It's also not entirely clear what the
utility/relevance of this information is in this particular document.
  • Loading branch information
@Trott
Trott committed Mar 28, 2019
commit 53a2b97f6bf0de7e9e9a9adb938d5e430f0a2836
7 changes: 0 additions & 7 deletions COLLABORATOR_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -681,13 +681,6 @@ label.
Attach the appropriate `lts-watch-` label to any PR that may impact an LTS
release.

#### How is an LTS release cut?
Comment thread
Trott marked this conversation as resolved.

When the LTS working group determines that a new LTS release is required,
selected commits will be picked from the staging branch to be included in the
release. This process of making a release will be a collaboration between the
LTS working group and the Release team.

## Who to CC in the issue tracker

| Subsystem | Maintainers |
Expand Down