Congrats to the team past and present! Nic -- Dr Nic Williams Stark & Wayne LLC http://starkandwayne.com +61 437 276 076 twitter @drnic

Good morning, good afternoon, good evening & happy Friday to you all, The cf CLI team GA'd the v7 CF CLI yesterday in the late afternoon. We're simultaneously excited, relieved, and exhausted by our

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

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,

Cripes - by which I meant "any future branch name changes". Not any future code changes. That'd be a bit extreme. Regards, Daniel 'Deejay' Jones - CEO +44 (0)79 8000 9153 @DanielJonesEB EngineerBetter

+1 for switching to "main", and for postponing any possible further changes until after that's done. Regards, Daniel 'Deejay' Jones - CEO +44 (0)79 8000 9153 @DanielJonesEB EngineerBetter Ltd - More

I spoke to Jan Dubois about the 'main' vs. 'release' consideration, and he found this PR: https://github.com/gitgitgadget/git/pull/655 which indicates that the new default branch name for `git init`

> in a BOSH world where CF jobs were running on the VM itself, as opposed to “inside containers on a VM”, BOSH did indeed take care of that part [but then also there wasn’t the task to keep the

Hi everyone, I really appreciate this effort, thanks Dieu for bringing this up! From reading this thread I get the understanding that we're now already discussing what the best name for the bfkam

Hi Ross, I haven’t tried Fargate myself (and I don’t know if this has been tried/is supported for CF on Kubernetes), but running CF on top of Kubernetes, “patching” might refer to two

I too agree with Jesse that in repos where you have `master` and `develop` branches, renaming `master` to `release` is more clear than using `main`. For repos that have just a single trunk branch I

Hi all,After the first day of the summit, while very interesting, it left me and my teammates with a question. With no Bosh, since Bosh is for VMs, how will patching be done, especially when you use

I agree with Jesse. Renaming from `master` is a great idea which I strongly support. `main` is similar but more inclusive, but perhaps we can take the opportunity to increase the semantic meaning of

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

Speaking for the CF Networking team, we're supportive. Shannon Coen (He/Him) Manager, Product Management scoen@... 875 Howard Street 5th Floor, San Francisco CA 94103 Mobile: +1.415.640.0272 From:

Hi all, I am also in support of this change after enquiring on slack. Cheers L -- Lee Porte Reliability Engineer GOV.UK PaaS Team ‪020 3920 6036‬ 07785 449292

Hi, everyone, The App Runtime PMC approved the proposal to retire the Perm project at today's PMC meeting. The corresponding project repositories are now located in the CF attic; see

I'm also in support of this change and would be happy to coordinate with the App Runtime project teams to apply it across their repositories. Best, Eric From: cf-dev@... <cf-dev@...> on behalf of

I support this change. From: cf-dev@... <cf-dev@...> on behalf of Dr Nic Williams <drnicwilliams@...> Sent: Tuesday, June 23, 2020 11:21:12 PM To: cf-dev@... <cf-dev@...> Subject: Re: [cf-dev]

I agree. Dr Nic-- Dr Nic Williams Stark & Wayne LLC http://starkandwayne.com +61 437 276 076 twitter @drnic