Release checklists

[sanket1729]

I think we should also have a release mini-checklist. So that we don't forget git tags, changelogs/release notes, and (optionally) crev proofs. Feel free to suggest more things if you think something is lacking. Thoughts?

[Kixunil]

For breaking releases:

• Did we update all dependencies?
• Is it worth doing semver trick?
• Do we need to write upgrade guidelines?

[tcharding]

Where would upgrade guidelines go? I'm also wondering if there is a better place for the new 'policy' doc I'm trying to introduce. Is there any reason not to add a docs directory to rust-bitcoin and make it, as we do for the github discussions feature, the central place for any org wide docs?

[Kixunil]

If it's reasonably short it could be in changelog, if long, we could have a separate file linked in the changelog. docs dir sounds good.

[tcharding]

Suggestions:

• Step 0: Do the release PR with version bump and changelog
• Step 1: Add a draft PR to miniscript that depends on the release PR branch from step 0 and link to it in the release PR.
• Step 2: Announce the imminent release by discussions announcement to make sure folks get a chance to put forward any open PRs for possible inclusion in the release
• Last Step: Make discussions announcement for target month for next 'feature freeze' (RC release) six months in the future.

[tcharding]

Check all instances of #[deprecated] introduced this release include a since = ... section with the correct version number.

[Kixunil]

Sorry, forgot since exists.

[sanket1729]

Slightly related checklist: #843