Document new branching steps
mateusoliveira43 opened this issue · comments
When a new branch (for a new OADP version) is created, some steps must be made. Document these steps.
References:
- #1226
- openshift/release#45664
- openshift/release#45692
- TODO restic CI PR
- Do not forget to metion vsm/volume-snapshot-mover for branches < 1.3
- add information about this file in CI docs https://github.com/openshift/release/blob/master/core-services/image-mirroring/konveyor/mapping_konveyor_latest
- talk about order and circular dependencies... openshift/release#45811
Do not forget to metion vsm/volume-snapshot-mover for branches < 1.3
Don't think we would be branching unless we're making new versions
Will finish this one first #1237 before working on this issue
Talk about build/ci-dockerfile https://github.com/search?q=repo%3Aopenshift%2Frelease%20ci-Dockerfile&type=code
add link to flake list https://github.com/openshift/oadp-operator/wiki/FRIGGIN-TIGER-FLAKES
update this as well https://github.com/openshift/oadp-operator/blob/master/Makefile#L441
also talk about cron in periodic jobs
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
/lifecycle frozen