EPIC: Refactor Release Process

[glnro]

Problem

The current Gaia release process is not sufficiently documented to facilitate current onboarding. Even with automation implemented like goreleaser for release generation, there are still manual processes and conventions that are not documented in RELEASING.md or anywhere else for that matter.

Closing criteria

Ensure documentation of every step of the release process:

• Creating a new release branch and updating mergify configuration
• Backporting features/fixes for releases (major & minor)
• Changelog generation
• Release Tagging
  • RC
  • Minor Release
  • Major Upgrade
• Publishing
• Notifying Communication Channels

Problem details

The release process is currently fragmented; even the automated workflows could be refactored. In addition to lacking documentation, changelog generation, release notes generation, and release communication could benefit from better automation either through the use of new tools or leveraging existing configurations.

Task list

Must have

Preview Give feedback

1. Update RELEASING.md to include comprehensive release cycle instructions #2357
   scope: build scope: docs +2
   
2. Use go-releaser configuration for releasing and release notes generation #2544
   automation scope: build scope: docs +3
   
3. Use unclog to manage and generate the changelog #2604
   +0
   
4. Update CONTRIBUTING.md to be consistent with the new process #2371
   scope: docs +1
   
5. test: Update test targets and add updated test docs #2397
   S: Productivity scope: build scope: docs scope: testing type: tech-debt +5

Nice to have

Preview Give feedback

1. Spike on configuring socials or a bot for release notification for go-releaser
2. Create UPGRADING.md in release/v* with info for upgrading to the new version
3. State-machine breaking is unclear #2401
   S: ImprovingThings scope: docs +2
   

Currently there is a WIP for updates to RELEASING.md