Re: Proposal to Rename the Primary Branch on all Cloud Foundry repos
|
Jesse Alford <jalford@...>
Could we consider using `develop` (and/or, where appropriate, `release` and version-specific branches) instead?
In addition to being problematic, `master` is confusing, as it means different things in different processes.
`develop`/`release` makes it clear what branch you're supposed to push/merge to.
As an example, `cf-deployment` currently has `develop` and `master`, with `master` being effectively a release branch - all releases are ff-only merges tagged on `master` with a version number. `main` would be less clear than `release` in this case - and, I
suspect, in many others.
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:
|
|
|