Our current (currently broken) release process is managed by Buildbot.
For numerous reasons it seems like we are at a fork in the CI road where a switch to GitHub Actions is an option.
We already have some of the release process handled by GitHub actions , the work needed to satisfy this issue would be re-implementing the Buildbot parts into a GitHub action context.
We can mark this issue is completed once we can run the release process for the next release candidate through GitHub.
Our current (currently broken) release process is managed by Buildbot.
For numerous reasons it seems like we are at a fork in the CI road where a switch to GitHub Actions is an option.
We already have some of the release process handled by GitHub actions , the work needed to satisfy this issue would be re-implementing the Buildbot parts into a GitHub action context.
We can mark this issue is completed once we can run the release process for the next release candidate through GitHub.