Hi,

 

Just my two cents.

I suggest a 4th option: Leave master as is, and make it read only. Branch off main from it and start contributing to the new branch.
Reasoning:

 

Thanks!

 

/George

 

From: Anton Komlev via TF-M <tf-m@lists.trustedfirmware.org>
Sent: Thursday, September 14, 2023 8:17 AM
To: Andrej Butok <andrey.butok@nxp.com>; tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: [TF-M] Re: Rename TF-M branches master -> main

 

Thanks, Andrew,

Indeed, (1) is the simplest if we all can afford it.

 

From: Andrej Butok <andrey.butok@nxp.com>
Sent: Wednesday, September 13, 2023 4:48 PM
To: Anton Komlev <Anton.Komlev@arm.com>; tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: RE: Rename TF-M branches master -> main

 

Voting for option (1),

to avoid deletion and confusion with syncing.

 

From: Anton Komlev via TF-M <tf-m@lists.trustedfirmware.org>
Sent: Wednesday, September 13, 2023 5:22 PM
To: tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: [TF-M] Rename TF-M branches master -> main

 

Hello,

 

Some time ago we planned to rename our master branch to main in all 6 repositories. There are multiple ways of doing that and I want to discuss with the community the best way suitable for all.
I can see the following options:

  1. rename master->main and use the main from one day.
  2. Create the main for contribution with main->master sync. Make master R/O and delete it in 3 months.
  3. Keep contributing to the master but syncing master->main.
  4. Other way?

 

I suggest option 2 but looking for better alternatives if any.

 

Thanks,

Anton