Hello CF community, here is the proposal from the release-integration and the credhub team about the generation and consumption of Secret passwords in cf-for-k8s. The proposal recommends, How

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

Hi all, I created an issue for routing-release for my team to do this work. https://github.com/cloudfoundry/routing-release/issues/171 Please feel free to use this as a template to make stories for

Late to pile on here, but congratulations to everyone that was involved in the v7 CPI and the CAPI v3 APIs... both recently with this big push AND historically. This has been a long time coming, and

Congratulations, Josh! Super excited to see the v7 CLI get its first GA release! Best, Eric

Congrats Josh and the CLI team. It’s a huge milestone for CF. — Sai Product Manager - CloudFoundry and PAS Release

It's been a long road. Congratulations on getting to GA! Shannon Coen (He/Him) Manager, Product Management scoen@... 875 Howard Street 5th Floor, San Francisco CA 94103 Mobile: +1.415.640.0272

Congrats to everybody involved! Regards, Bernd From: <cf-dev@...> on behalf of Dieu Cao <dieuc@...> Reply-To: "cf-dev@..." <cf-dev@...> Date: Saturday, 27. June 2020 at 02:11 To: "cf-dev@..."

Congrats! Huge milestone and awesome effort from everyone involved! -Dieu

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

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