Project

General

Profile

Actions

Issue #2302

open

Deprecate the use of "master" over "main" on source code Repositories

Added by _I3^ RELATIVISM almost 3 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Low
Category:
Infrastructure (web, git)
Target version:
Start date:
01/29/2022
Due date:
% Done:

0%

Estimated time:
4.00 h
Resolution:
Device:
Not device specific
Grant:
Type of work:
System administration, Wiki editions

Description

The use of the word main does not make a procamation to hyerarchical structures.

Replicant has a project should try to use the term main instead, Is also much more intuitive given it is subentended that it is the main source code branch

Cheers Alexis

Actions #1

Updated by Denis 'GNUtoo' Carikli almost 3 years ago

The name main indeed reflects more closely what the branch is used for.

I've already started using main for new repositories, but we also have more than a hundred repositories, so it's not trivial to do the migration for existing repositories.

Migrating a given repository is easy enough, we could rename master to main and make a link from master to main (to keep compatibility with potential existing users).

Once the code from master is pushed to main we could delete the master branch and run the following commands:

git symbolic-ref HEAD refs/heads/main # Change the main branch
git symbolic-ref refs/heads/master refs/heads/main

The main issue here is rather to find which repositories to migrate.

As I understand it only makes sense to migrate the repositories we created and not the mirrors nor the forked repositories:
  • Mirrors are simply mirrors of the upstream code so it doesn't make sense to change their content (apart from choosing at revisions they should be mirrored)
  • If we rename upstream branches names in the forked repositories, it would be confusing.

So we need to make a list of repositories that are not forks:

Actions #2

Updated by Denis 'GNUtoo' Carikli almost 3 years ago

In /replicant we have at least the following repositories that are not forks:
  • hardware_replicant_libsamsung-ipc
  • hardware_replicant_libsamsung-ril
  • packages_apps_replicantwallpapers
  • vendor_replicant_artwork.git
  • vendor_replicant-data.git
  • vendor_replicant-release-scripts.git
  • vendor_replicant-scripts.git
The following are not forks but also don't have any master branche:
  • bootable_bootloader_goldelico_gta04
  • bootable_bootloader_goldelico_gta04_x-loader
  • device_goldelico_gta04.git
  • device_goldelico_gta04_u-boot.git
  • kernel_goldelico_gta04.git
Actions #3

Updated by Denis 'GNUtoo' Carikli almost 3 years ago

  • Type of work Wiki editions added

We probably also need to modify the Replicant contributor guide to reflect that.

Actions

Also available in: Atom PDF