ansible
Document branching process
We should document the process of branching for a new ansible-core release train, including updating https://github.com/ansible/ansible-documentation/blob/devel/docs/ansible-core-branch.txt, updating the pip-compile job as mentioned in https://github.com/ansible/ansible-documentation/issues/1765, and any other changes that need to be made.
Thanks for creating this issue @gotmax23 I've assigned it to myself and added the DaWGs label. Maybe someone from that meeting will want to get involved and ask some questions, do a review, and possibly volunteer to try going through the process for 2.18.
@oraNod - Do we know if general community members have the rights to do this? I know I did it once but I can't remember if it required maintainer rights in this repo or not...
A maintainer needs to create the branch, but after that, anyone can theoretically submit a PR against it to make the necessary changes.
Also:
rm -r .github/workflows/pip-compile-dev.yml .github/workflows/pip-compile-docs.yml .github/workflows/reusable-pip-compile.yml hacking/tagger tests/tag.*
sed -i '/-r tag.in/d' tests/typing.in
and remove "hacking/tagger/tag.py" from the LINT_FILES tuple in noxfile.py.