Switch Release branch policy to always match up 1-to-1 with pulpcore release branches

Open gerrod3 opened this issue 2 years ago • 2 comments

Currently this repo's release branches are always one behind the latest release for tagging purposes, but this is confusing to outside contributors. Switch it to be aligned with pulpcore (and all other plugins) release branching strategy.

Jun 14 '23 17:06 gerrod3

FYI: This involves the main branch being only used to build nightly, not to build stable.

Jun 20 '23 15:06 mikedep333

https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#create

This could help

Jun 20 '23 15:06 decko