doc: update backport requirements on LTS lines

[aduh95]

Refs: #34950 (comment)

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• documentation is changed or added
• commit message follows commit guidelines

cc\ @richardlau @jkrems

[jkrems]

Thanks for keeping these in sync with practices! But I think what should have happened here that the back port requested label should either not have been added or removed (if it was active while the version moved into maintenance mode).

Maybe it would be better to make it two sentences, the latter being something along the lines "backports for feature additions shouldn't be requested for maintenance versions"?

[BethGriggs]

Yes, the label was added when v10.x was still in Active LTS. (It looks like we still have 131 with that label.)

Adding release-agenda so we can discuss in our next Release WG meeting. I do think we need some process around auditing/removing backport-requested-vN.x labels when a release line transitions from Active LTS to Maintenance.
/cc @nodejs/release

[BethGriggs]

We discussed this in the Release WG meeting last week (nodejs/Release#609) and agreed that we should delete the backport-requested-vN.x label when a release transitions between Active LTS and Maintenance. #35224 updates our documentation to include this.

[aduh95]

@BethGriggs #35224 has landed, should I close this?

[BethGriggs]

@aduh95 I think so, yes