Re: Proposal: Plan to Deprecate cf-release

David Sabeti

Hi Benjamin,

The README is still accurate, and we're working away at being able to make
some guarantees about uptime during deploys -- especially the deploy to
transition from cf-release to cf-deployment. This is the tracker milestone
<> to keep an eye on,
which we're currently targeting for end of July. Once we feel comfortable
with the uptime measurement, we'll announce it pretty loudly that
cf-deployment is ready to go and give it a 1.0.0 version.


On Fri, Jun 23, 2017 at 12:50 PM Benjamin Gandon <benjamin(a)>

Super cool to get to know this new “cf-deployment-transition” repo!

But about cf-deployment *in production*, is it still blocked on “Downtime
testing” as the README states? Or has there been progress on that without
it being reflected in that README?

If it is still a blocker, could you give us insights about what is
actually blocking, and any link to a tracker story so that we can watch
progress about that?

/Benjamin (depuis mon iPhone)

Bien cordialement,
/Benjamin Gandon (depuis mon iPhone)
Le 23 juin 2017 à 01:55, David Sabeti <dsabeti(a)> a écrit :

Hi cf-dev,

As cf-deployment <> moves
closer to general availability (GA), we want to propose a schedule for
deprecating cf-release <> and
helping operators move from deployments based on cf-release to deployments
based on cf-deployment. Please take a look at the proposal included here:

*We're hoping to finalize a plan by July 3rd, so please leave any feedback
on the document by then.*

David Sabeti
Project Lead, CF Release Integration

Join { to automatically receive all group messages.