Re: Proposal to Rename the Primary Branch on all Cloud Foundry repos
|
Jesse Alford <jalford@...>
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:
|
|
|