doc: remove incorrect information from README

[Trott]

The README had a list that was supposedly the only types of changes that
land in LTS branches. However, other types of changes have landed there
routinely. Rather than try to codify, removal is a tacit acceptance that
we land whatever Release WG deems appropriate.

Refs: #405 (comment)
Refs: #405 (comment)

@MylesBorins @devsnek

[MylesBorins]

We don't yet have consensus that we are adopting this as a long term change... the 8.x maintenance minor release coming out may be a one off.

I realize that isn't ideal, but I am not in favor of us just removing these constraints as a general guidance for maintenance LTS

[richardlau]

This paragraph needs to stay -- It basically defines what being in Maintenance mode is. We have been following this for Node.js 6.x.

Node.js 8.x is an oddity in that according to the original schedule it shouldn't be in Maintenance until April but it was brought forward to January at the end of last year. So far nothing in #405 has actually landed in an 8.x release and the things being discussed there are not guaranteed to land either (in fact this very paragraph, unless changed, should be the guidance as to what is accepted).

[Trott]

@richardlau I've restored that paragraph. PTAL.

[Trott]

I am not in favor of us just removing these constraints as a general guidance for maintenance LTS

That's kinda the problem, though. They are presented as constraints but treated as general guidance.

Maintenance paragraph restored

[mhdawson]

How about just changing

Changes in an LTS-covered major version are limited to:

to

Changes in an LTS-covered major version are limited to the following unless reviewed and approved by the Release Working Group members:

[Trott]

Changes in an LTS-covered major version are limited to the following unless reviewed and approved by the Release Working Group members:

Doesn't Active LTS get all semver-patch and semver-minor changes if they cherry-pick cleanly?

[MylesBorins]

Nope. Every commit goes through a separate review with different expectation then current

…

On Wed, Mar 20, 2019, 7:14 PM Rich Trott ***@***.***> wrote: Changes in an LTS-covered major version are limited to the following unless reviewed and approved by the Release Working Group members: Doesn't Active LTS get all semver-patch and semver-minor changes if they cherry-pick cleanly? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#426 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV64qU1TRWlcZsW8rSUPnUWWP_UlWks5vYsC-gaJpZM4b-Xdp> .

[Trott]

Nope. Every commit goes through a separate review with different
expectation then current

I'm not sure what "separate review with different expectation then current" means, but I can also tell this is going nowhere so I'm going to close this.

[Trott]

but I can also tell this is going nowhere so I'm going to close this.

Thanks to anonymous friend-who-has-my-back, I'm back here to say: I've been tipped off that the text above sounds snippy and annoyed. And sure enough, it does. Sorry. Didn't mean it that way. Meant it more like this:

I was offering this as a quick remedy but it looks like this isn't going to fly so someone else will have to do a real fix on the doc. Oh, well. I'll close this.

Didn't want to be a jerk to the Release Team, whose heavy workload is inadequately appreciated!