Hi folks, A few years ago we had the initalitive to get rid of problematic terms like "master"/"slave". Git changed its default branch name to 'main', we changed our default dist-git name to 'rawhide' (*). We also adjusted various terms in documentation in many places.
But some pockets of stale naming remain. It'd be great to finally clean this up and achieve consistency! For owners of various repos, can you please do just do the rename. Users will understand and adjust (**). I'm aware of: - https://pagure.io/packaging-committee/tree/master, a.k.a. https://pagure.io/packaging-committee/issue/1098. - anything with 'master' in https://gitlab.com/fedora/docs/docs-website/docs-fp-o/-/blob/stg/site.yml#L109 Please reply with other examples so we can have a TODO list. (Not just branch names, but that is the least-effort/most-obvious place to start.) Zbyszek (*) In hindsight, using a branch name that matches its purpose seems … natural. Why didn't we do this earlier? (**) I use: git fetch origin --prune && git remote set-head origin -a && git switch rawhide && git branch -d master for dist-git repos, and for repos with a 'main' branch: git fetch origin --prune && git remote set-head origin -a && git switch main && git branch -d master -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
