doc: enforce strict policy to semver-major releases

[RafaelGSS]

Refs: nodejs/Release#1054

This needs to be discussed first by the @nodejs/releasers. However, since the next session (nodejs/TSC#1648) might not happen due to NodeConf/Collab Summit I thought would be better to discuss it async.

cc: @nodejs/releasers @BethGriggs

[nodejs-github-bot]

Review requested:

• @nodejs/tsc

[github-actions]

The notable-change PRs with changes that should be highlighted in changelogs. label has been added by @RafaelGSS.

Please suggest a text for the release notes if you'd like to include a more detailed summary, then proceed to update the PR description with the text or a link to the notable change suggested text comment. Otherwise, the commit will be placed in the Other Notable Changes section.

[RafaelGSS]

Adding blocked label to make sure we will land it only when we get releasers consensus.

[aduh95]

As is, it's wrong to say this PR enforces the strict policy, the commit message is a bit misleading. You could say "clarify", or maybe "stiffen".

IMO, this should either go in the collaborator-guibe.md document (if we expect non-releasers to comply with that policy), and/or the collaborator guide should forbid non-releasers to land semver-major PRs (I don't think we want to do that). If we want the policy to be enforced, the CQ should probably be updated to skip semver-major PRs until the branch-off.

[RafaelGSS]

I think landing a semver-major PR on main days/weeks before the semver-major release is ok. It doesn't mean that the commit will be included in the major release. My goal with this doc change is to clarify/enforce that the last sync between main and vN.x will be a month prior to the release. I might be using the wrong word, but I do think "enforce" should mean we won't include any semver-major PR that was merged into main less than a month of the release date (except in specific situations as mentioned in the doc too)

[aduh95]

Oh I didn't read it like that, so you mean like the following?

Suggested change

	No `SEMVER-MAJOR` pull requests should be landed within one month prior to
	the major release date, unless there is consensus from the Node.js releasers
	team to do so. This measure aims to ensure better stability for the release
	If a `SEMVER-MAJOR` pull requests lands on the default branch within one month prior to
	the major release date, it must not be included on the new major staging branch, unless there is consensus from the Node.js releasers
	team to do so. This measure aims to ensure better stability for the release