docs(release): v1.30.0, v1.31.0 and v1.31.1 release template improvements

[rjan90]

Related Issues

#12480 and #12344, #12827

Proposed Changes

Accumulating release template improvements from shipping the v1.30.0, v1.31.0 and v1.31.1 release

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title conforms with contribution conventions
• Update CHANGELOG.md or signal that this change does not need it per contribution conventions
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[rjan90]

Just adding as a note to myself. We should add a step in here to remove the content:

[rjan90]

For later, wondering if we should move the "Remove the "backport" label from all backported PRs" to after merging the PR. That will make it easier for others reviewing if something has been missed out:

[BigLep]

2024-11-12 discussion idea: to avoid text duplication between the changelog and the release page, just have the release page point to the changelog.md file rather than copy/paste. One minor benefit beyond avoiding copy/paste is that then don't have to worry about when changelog.md links to other markdown files.

[BigLep]

There are some template changes happening in #12741

[BigLep]

2024-12-04: add some collapse sections to the template so that the uncollapsed/open section is what's actively being worked on. This will be less scrolling and clearer on where to focus.

[BigLep]

I think the post release steps should include ensure lotus-docs and filecoin-docs are updated (which should ideally just mean merging a PR that was automatically created).

[rjan90]

2025-01-20:

• Rebased the PR onto latest master
• Added sections to the release template.

[rjan90]

I updated some text related to where one should fork off from when publishing a patch release in: 50a550d

I did this because in the Release Flow documentation we say:

- PATCH releases contain backwards-compatible bug fixes or feature enhancements.
- Releases are almost always branched from the master branch, even if they include a network upgrade. The main exception is if there is a critical security patch we need to rush out. In that case, we would patch an existing release to increase release speed and reduce barrier to adoption.