doc: remove "How is an LTS release cut?" section · nodejs/node@28efecc (original) (raw)

`@@ -30,11 +30,8 @@

`

30

30

`- I Made a Mistake

`

31

31

`- Long Term Support

`

32

32

`- What is LTS?

`

33

``

`-

• How does LTS work?

`

34

``

`-

• Landing semver-minor commits in LTS

`

35

33

`- How are LTS Branches Managed?

`

36

34

`- How can I help?

`

37

``

`-

• How is an LTS release cut?

`

38

35

`* Who to CC in the issue tracker

`

39

36

``

40

37

`This document explains how Collaborators manage the Node.js project.

`

`@@ -681,13 +678,6 @@ label.

`

681

678

`` Attach the appropriate lts-watch- label to any PR that may impact an LTS

``

682

679

`release.

`

683

680

``

684

``

`-

How is an LTS release cut?

`

685

``

-

686

``

`-

When the LTS working group determines that a new LTS release is required,

`

687

``

`-

selected commits will be picked from the staging branch to be included in the

`

688

``

`-

release. This process of making a release will be a collaboration between the

`

689

``

`-

LTS working group and the Release team.

`

690

``

-

691

681

`## Who to CC in the issue tracker

`

692

682

``

693

683

`| Subsystem | Maintainers |

`