Proposal: change branching model from 'release from stable branch' to 'release from main branch' from 4.0.0 on

[felixfontein]

SUMMARY

I'm proposing to change the release model from "release current major version from stable branch" to "release current major version from main branch" ("Hybrid approach").

Right now this collection is mostly unmaintained, and has a very low amount of releases. The "release from stable-X" approach for major version X is ok for collections that have a larger amount of contributions, like community.general, but for a collection like community.network which is struggling to get things merged, has no proper maintainers, and has only seldom releases at all, it's overkill. Also it puts a lot more burden on new maintainers since it's a lot more complicated than doing releases from main. (Obviously releases for older release branches still need to be done from stable-Y branches.)

ISSUE TYPE

• Feature Request

COMPONENT NAME

release process

[ansibullbot]

Files identified in the description:
None

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help