In-Reply-To=<e5d8cb0e8110f79c8fe0cfb9a508c4b6%40posteo.de> Hello, renaming is done. Be aware to update your local repositories or re-clone them; also your forks on GitHub. Beside the new "main" branch I created the "dev" branch. In the past I used the name "develop" but found out it is unusual and a bit to long. I think "dev" is easier (for some of us). :D Hope this is OK. I also updated the target branch in all existing and open Pull Requests. I created a new Pull Request updating version numbers, changelog and mention the "dev" branch in the README.md. @Jürgen: I know you work on some FAQ and maybe README. Maybe this will cause a merge conflict. But some md-files are a secure learning case I think. ;) I assume your upcoming docu changes should go into "main" too? I suggest to merging it into "dev" and then picking the changes form there into "master". I would do that via "git checkout my.file dev". I never used git's cherry pick before. This is one exception of the only-release-commits-in-main because "main" do produce the landing page via its README.md. Kind Christian