Re: Rename "master" branch to "main"?

[Carlos O'Donell <carlos@redhat.com>]

On 1/21/21 12:06 PM, Mike Frysinger wrote:
> On 21 Jan 2021 08:30, Carlos O'Donell via Libc-alpha wrote:
>> On 1/20/21 7:23 PM, Mike Frysinger wrote:
>>> On 20 Jan 2021 08:49, Carlos O'Donell via Libc-alpha wrote:
>>>> Having said that, I don't know how to do
>>>> a redirect to keep old branches working (though I've seen it done in
>>>> Fedora when we wholesale moved from /foo to /rpms/foo).
>>>
>>> what branches are you thinking of ?  the old release branches ?  tbh, i
>>> think we should just look forward.  lets focus on refs/heads/master ->
>>> refs/heads/main.  changing that branch requires updating hooks and such,
>>> but no other branches should break.
>>
>> I am only thinking of master->main. Consensus was not to change any release
>> branches.
>>
>> I would like the master->main transition be possible to do with a redirection
>> so we don't break existing checkouts and scripts.
>>
>> I think that transition can be done with redirection because I saw something
>> like this done in Fedora, but I haven't reviewed the solution.
> 
> i noted earlier that i was able to set up a redirect on my server:
> 	$ cat refs/heads/master
> 	ref: refs/heads/main
> 
> setting up a redirect to ease people/scripts over to "main" sounds great,
> but imo, we shouldn't leave it there forever.  scripts will need to change.
> if the point is to bury master, leaving it as a perm symlink defeats that.

I think Fedora left the link there for a year. That's fine with me. We also
announce it far and wide that it's changing. When the link was in place in
Fedora git kept issuing an annoying message reminding you it was doing
a redirect and that was useful to remind you to update your repo.
 
>> The problem of redirecting one branch, or all branches is effectively the
>> same problem just solved once (and then solved later again if we want).
> 
> right, i just wanted to make sure we weren't going to stall waiting for a
> complete solution for everything when we have a path for refs/heads/master.
> 
> for the wiki page, doesn't seem like we've been great at organizing into
> namespaces.  we do have "GlibcGit" though, so maybe the page would be:
> 	https://sourceware.org/glibc/wiki/GlibcGit/MigrationToMain

Sure.
 
> if that sounds fine, i can populate it with the content we've already
> produced in these threads.  obviously the real work is left to an admin
> (i.e. you) as the rest of can only backseat drive ;).

Having a checklist is *immensely* helpful.

-- 
Cheers,
Carlos.