Create a Release Issue Template

[rjan90]

Done Criteria

• The template includes sections for:
  • Pre-release checklist
  • PR preparation steps
  • Review process
  • Post-merge steps (tagging, publishing)
  • Verification steps
• All steps from the CONTRIBUTING.md file's "Releasing" section are incorporated
• Additional steps or checks that are currently tribal knowledge are added

Why Important

Creating a comprehensive release issue template will standardize our release process, reduce the risk of missing critical steps, and make the process less dependent on tribal knowledge. This will improve the consistency and reliability of our releases, making it easier for both new and experienced team members to manage the release process.

User/Customer

• FVM team members responsible for releases
• Contributors preparing release PRs
• Maintainers reviewing and merging releases

Notes

• Consider creating separate templates for primary FVM crates and other crates if the processes differ significantly

[BigLep]

@Stebalien: I put this one done on your Knowledge Transfer Board - let me know if you disagree?

Or actually, @rjan90 , it looks like you have been releasing? Is there a release template you've been following or do you feel comfortable creating it?

[rjan90]

Or actually, @rjan90 , it looks like you have been releasing? Is there a release template you've been following or do you feel comfortable creating it?

I can create it - and just get a ✅ on the template from Steb.