Hi Mike, The tracker issue to follow is here <https://www.pivotaltracker.com/story/show/144128279>. Please do not hesitate to reach out if you have any questions, thanks. Best, Abby

Thanks Abby, Is there a tracker issue or something we can follow to get updates as they are discovered? Mike

Congrats! This is awesome 👏 wrote:

Hi, all, Related to this change in BOSH releases for the cflinuxfs2 rootfs, the manifest-generation script in Diego v1.14.0 now allows operators to use the "-r" flag to opt into the cflinuxfs2

Hi CF Devs, It was recently discovered that routing release versions 149-151 includes a bug whereby increased latency and 502s can be observed. If you have deployed cf-release 256 or greater, you

What's really wonderful about this, IMO (as one example of many), is seeing how focused the CF technical community is on meaningful changes that are clearly the result of maturing users and well

Congrats to Ben and team! -Dieu

I’m pleased to announce the release of Java Buildpack 4.0. This release has been a big effort for the team over the last couple of months and is the culmination of a major focus on improving how

Hi all, We have been working on the milestones proposed before in order to lessen and remove our dependencies on Consul. Please see the updated Locks & Service Discovery in CF

So exciting! Congrats to the BOSH Windows team! wrote:

By this we mean this is the technology that will put us on the path to full feature parity. We do, however, have a active track of work to scope and deliver persistence on Windows VMs. As far as full

I note that your announcement says "This enables feature parity with BOSH-deployed Linux VMs”. Does this mean it now supports persistent disk on windows? Or is this only “feature parity” wrt

Amazing! Great work BOSH Windows team! -- Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815

Hi cf-dev, This is a very exciting email to write! I'm extremely proud to announce that BOSH Windows, the new deployment mechanism for Windows cells, is now generally available! ACTION REQUIRED:

Hi Gwenn, We agree that this change is important. However, the Open Service Broker API Change Policy [1] specifies the following: New fields may be added to existing request/response messages. These

HI, I think this change is important and need to be done, I like the new context parameters but not sure about the `optional`, I think it's important to which env. / platform we are talking

The Open Service Broker API [1] working group have created a proposal [2] to make the Service Broker API less CF-specific. The proposed changes will help grow the services community by allowing

CF Devs, Please see information for the following high UAA CVE. This issue was fixed in the same releases as CVE-2017-4972 (the blind SQL injection) so if you already have plans to upgrade, you don't

Hi All, To reduce the size of the .NET Core buildpack and discourage the use of unsupported versions of .NET Core, we will be removing the following SDK versions: 1.0.0-preview2-1-003177 As well

Hi All, Quick follow-up to this. To ease the transition, we're going to continue updating the current cflinuxfs2 BOSH release[1] until May 19, 2017. After May 19, 2017, only the new BOSH release[2]