ssp-operator
ssp-operator copied to clipboard
Automate release procedure
Create a script for creating github release, so we don't forget any of the steps.
For new major release:
- Create a new
release-vX.Ybranch frommain. - Create a tag
vX.Y.Zonrelease-vX.Ybranch. - Create Github release from this tag. It's important to set
target_commitishtorelease-vX.Ybranch. CI uses it. - Create an annotated tag
api/vX.Y.Zpointing to the same commit asvX.Y.Z. This is needed to make theapisubmodule accessible. - Post a PR to https://github.com/openshift/release repository to activate CI for the new
release-vX.Ybranch.
For new minor release:
- The same steps as above, but without creating a new branch and creating PR to https://github.com/openshift/release .
When that script (I believe CI job) will be executed? by a manual trigger, e.g. clicking on a button to execute CI job that will execute that script?
Deciding that is part of this issue.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle rotten
We can run the script as a github action that is manually triggered from the github website.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
/remove-lifecycle stale