Staging and Releasing Strategy

[rainerleber]

Each PR should contain a changelog fragment:
https://docs.ansible.com/ansible/latest/dev_guide/developing_collections_changelogs.html

A Dev Branch is not necessary in my opinion because of the following reasons:

• Each change small or big should be done with a separate branch the branch with the feature could be integration tested and only merged if all tests are successfully either automated or manually.
• Smaller PRs are reviewed by 1-n people and if it's approved it's ok for every one
• BIG release PRs from dev to main are hard to review. If we stage each tested change to main for example there is no value for a dev branch.
• If only the main branch is used a release could be created more quickly without the need of asking people for review the staging.
  Because it's reviews before the merge.
• Main must not be in the same state as the release because the release marks stable point not the main branch.
• The code could be seen in the release tar ball
• Roles in Main are the upstream and could be used for test and could contain fixes or features. It's possible to use it faster by the users and must not wait until it is staged and merged.
• Much more time is needed

There are a lot more advantages I can talk about but this are a few arguments to stop developing with a dev branch.

[rainerleber]

@sean-freeman @berndfinger @rhmk @ja9fuchs