---
# System prepended metadata

title: renaming 'master' branch in git repos

---

# renaming 'master' branch in git repos

## timeline / schedule

- [ ] flatpak namespace on dist-git - soon?
- [ ] infra / releng repos - ?
- [ ] rpms namespace on dist-git - after f33?
- [ ] other dist-git namespaces - after f33?

## areas

### src.fedoraproject.org / dist-git

* flatpak namespace
* rpm namespace
* modules namespace
* tests namespace
* containers namespace

### releng/infra

* releng
* fedora-infra/ansible
* Upstream projects
  * pungi-fedora
  * lorax-templates
  * fedpkg
  * fedsm-admin
  * ...

### github / apps

* fedora-infra/* ?
* pagure.io/... ?

## options

1. Move master branch to new name, leaving master branch gone, change default pagure branch to new name.

* clean break
* might cause problems for existing checkouts
* might cause confusion for existing checkouts
* (-) not backward compatible

2. Move master branch to new name, leave master branch with README.md file explaining the change, change default pagure branch to new name.

* leaves master branch around
* explains what happened better to existing checkouts
* (-) not backward compatible
* (-) is a lot more work since we'll need to clone/commit/push to every single repo while the other solutions can entirely be done server-side

3. Change the default branch and symlink the default branch to `master` branch. All the new repos will have the new default branch without any symlinks.

* Leaves the master branch around
* People can still access it as they are doing it right now.
* But, this means we keep the `master` branch around and we might not remove them forever.
* Most backward compatible way but also the one with the less incentive to change behaviour

## naming

'main' - +1 (mohan) +1 (pingou) +1 (tomas)

'develop' - 

'rawhide' - (doesn't really suite the flatpak development model - pingou)
'?'