Re: Proposal to Rename the Primary Branch on all Cloud Foundry repos


Dieu Cao
 

Hey all,

I really appreciate the support on this thread for moving away from `master` as the default branch.
It seems `main` is a popular choice as an alternative default and some projects are moving to adopt that.
It sounds like each PMC can take that as a suggestion, in addition to the other alternatives suggested on this thread, and figure out what they would like to standardize on within each PMC.
I'd like to recommend, as a way to move this forward, that each of the PMCs work towards guidance on defaults within their PMCs and each PMC work towards achieving those changes.

Thanks all,
-Dieu


From: cf-dev@... <cf-dev@...> on behalf of Amelia Downs via lists.cloudfoundry.org <adowns=vmware.com@...>
Sent: Tuesday, June 30, 2020 8:44 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev@...>
Subject: Re: [cf-dev] Proposal to Rename the Primary Branch on all Cloud Foundry repos
 
Hi all, 

I created an issue for routing-release for my team to do this work. 


Please feel free to use this as a template to make stories for your own teams/repos/components.

Best, 
Amelia

From: cf-dev@... <cf-dev@...> on behalf of Jesse Alford via lists.cloudfoundry.org <jalford=vmware.com@...>
Sent: Friday, June 26, 2020 10:16 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev@...>
Subject: Re: [cf-dev] Proposal to Rename the Primary Branch on all Cloud Foundry repos
 
Changing branches breaks a lot of tooling, docs, and expectations.

If you're going to do it - which to be clear I think we should in this case -
it is better to move to what you'd prefer,
rather than make multiple such breaks.

I agree that `main` is a fine default and matches what Github will be migrating to.
If "default branch, plus whatever expectations you might bring with you about such a branch"
is what you want to communicate with your branch name, switch to `main`.

If "the place that active development should be pushed/merged to" and,
optionally,
"the place that deliberately released code should be pulled from"
is what you want to communicate, maybe use that pattern.

If you want to say something else with your branch names,
this is an opportunity to communicate.

Anyway. I support changes away from `master`,
but think we don't need to coordinate further on the matter.

From: cf-dev@... <cf-dev@...> on behalf of Josh Collins <collinsjo@...>
Sent: Friday, June 26, 2020 9:58 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev@...>
Subject: Re: [cf-dev] Proposal to Rename the Primary Branch on all Cloud Foundry repos
 
I support this change.

Josh Collins - CF CLI PM

From: cf-dev@... <cf-dev@...> on behalf of Lee Porte via lists.cloudfoundry.org <lee.porte=digital.cabinet-office.gov.uk@...>
Sent: Wednesday, June 24, 2020 12:22 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev@...>
Subject: Re: [cf-dev] Proposal to Rename the Primary Branch on all Cloud Foundry repos
 
Hi all,

I am also in support of this change after enquiring on slack.

Cheers

L

On Tue, 23 Jun 2020 at 23:06, Dieu Cao <dieuc@...> wrote:
Hey all,
I would like to propose that the cloud foundry projects rename the primary branch on all https://github.com/cloudfoundry and https://github.com/cloudfoundry-incubator repos to “main” as part of Cloud Foundry’s commitment to an inclusive and welcoming community.
I believe some project teams independently have plans to invest in making this change.
Thoughts? Feedback?
-Dieu



--
Lee Porte
Reliability Engineer 
GOV.UK PaaS Team
‪020 3920 6036‬
07785 449292

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.