User:Nex/Maintainer-Notes/Version bump and stabilization workflow

This is my workflow when adding new versions and how to start the stabilization process.

Getting updates on new versions
To receive updates about new versions, go to the upstream page (usually GitHub, GitLab, etc.) and enable custom notifications for releases. To receive notifications for serious issues, notifications for issues should be enabled as well.

New versions
When a new release is published upstream, check out the new version of the repo locally an diff against the old version to check for notable changes which might affect dependencies and/or the the commands in the ebuild.

Copy the old ebuild (or the live ebuild template) to the new version, optionally adjust the ebuild to account for aforementioned notable changes. If necessary, adjust the live ebuild before copying so both ebuilds receive the update. Dont forget to remove stable keywords for the new ebuild:

Now the ebuild needs to be compiled and tested. If everything works as expected, the changes can be commited and a PR can be opened for ::gentoo.

Stabilization reminder
The new version shall be stabilized according to the devmanual. To set up a TODO item in Taskwarrior, run

Where X is the day where the stabilization shall happen. Wait is set so that the task isn't show before it's actually important to think about stabilization (i.e. a few days before it can be stabilized). To highlight the task on the day where the stablereq shall happen.