You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Michael Bouschen (Jira)" <ji...@apache.org> on 2021/04/14 16:22:00 UTC

[jira] [Updated] (JDO-793) Decide whether to rename the 'master' branch to 'main'

     [ https://issues.apache.org/jira/browse/JDO-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Bouschen updated JDO-793:
---------------------------------
    Component/s: site and infrastructure

> Decide whether to rename the 'master' branch to 'main'
> ------------------------------------------------------
>
>                 Key: JDO-793
>                 URL: https://issues.apache.org/jira/browse/JDO-793
>             Project: JDO
>          Issue Type: Task
>          Components: site and infrastructure
>            Reporter: Tobias Bouschen
>            Priority: Minor
>
> There still is an ongoing discussion over the use of the word 'master' in the context of branches in versioning systems. The most common new name is 'main'.
> If we were to change the name of the 'master' branch, the following things would have to be done as well:
>  * Adjust the references to the 'master' branch in the '.asf.yaml' files
>  * Adjust the references to the 'master' branch in the GitHub workflow files (located in '.github/workflows/')
>  * Inform INFRA to change the default branch for GitHub and GitBox
>  * Release instructions on how to adjust the local workspace (uses 'main' as the new name as an example)
>  ## Rename the branch:
> {code:java}
> git branch -m master main{code}
>  ## Fetch from origin: 
> {code:java}
> git fetch origin{code}
>  ## Set the origin for the new branch:
> {code:java}
> git branch -u origin/main main{code}
>  ## Change the symbolic reference for HEAD:
> {code:java}
> git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)