Sunshine: create release documentation for maintainers

[ReenigneArcher]

Is there an existing issue for this item?

• I have searched the existing issues

Repositories

LizardByte/Sunshine

Languages/Skills/Technologies

Markdown

Description

I made a couple of mistakes in the last two releases, so would like to add some maintainer docs for releasing.

These are notes for what should be in there.

1. Before making a release stable/latest, make sure the copr-ci workflow has completed and it has updated the release notes and assets with the RPM and virus total results.
2. To make a release stable, edit the release in GitHub UI. Modify the release notes as needed and uncheck pre-release.

• normally non user interfacing changes are removed
• security updates should be added to the top
• highlights of new features and big fixes can be below security fixes if there are any

3. More workflows will run once this happens (will be adding deployment URLs for these add deployment/environments to CI/CD #116)

• copr-ci again, but for stable repo instead of beta
• update docs
• update changelog
• publish to flathub (PR will need to be merged by @ReenigneArcher)
• publish to pacman-repo (PR will need to be merged by @ReenigneArcher)
• publish to winget (Microsoft will decide to merge or not)
• publish to homebrew (automatically commited, no PR)

Estimated Effort

effort:Medium

Priority

priority:High

Target Milestone

1-3 months

Dependencies

Depends on #116