+0
No objection if it changes. It will take me a while to get used to it as none
of the projects I contribute to have changed to main yet (since GH changed the
default branch name).
Bruno
p.s. voting +0 as in my native language (Portuguese) and other languages that I
am a bit familiar with (Japanese/Spanish) this word has a different (normally
positive) connotation (the word for master from slavery or lordship is
different). And I still see this word used in other situations in English
(master-at-arms, master bedroom, master bath, chessmaster, kung fu master,
master degree, soccer masters/seniors, master data model, master data
management, etc). I think the case for Jenkins master/slave was a good move,
but IMO master branch in git always had the meaning of main, as in master data
model.
On Saturday, 6 February 2021, 12:03:11 am NZDT, Andy Seaborne
<[email protected]> wrote:
+1
On 05/02/2021 10:04, Andy Seaborne wrote:
> This is a decision by lazy consensus[*].
>
> Let's rename the default branch as 'main' for both the code repo and the
> site repo.
>
> The process is:
>
> 1/ We create a repo branch 'main'
> 2/ Ask infra to make it the default
> 3/ We remote delete 'master'
> 4/ Update build jobs in Jenkins
> 5/ Update the site build job on Jenkins
> (via the "Jenkinsfile" in the jena-site repo)
>
> and on local copies after step 2:
>
> # Rename locally
> git branch -m master main
> # Set tracked branch
> git fetch origin
> git branch -u origin/main main
>
> I think github forked repos and PRs automatically switch.
>
> Andy
>
> [*]
> Lazy Consensus:
> https://community.apache.org/committers/lazyConsensus.html
>
> Default to agree, wait 72 hours.
> but adding +1 is nice.
