Hi cf-dev,

As cf-deployment <https://github.com/cloudfoundry/cf-deployment> moves
closer to general availability (GA), we want to propose a schedule for
deprecating cf-release <https://github.com/cloudfoundry/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:

https://docs.google.com/document/d/1KLl4UIQbl92SvYom4fO-LcEoMK1D45KmjA988MwnOR4/edit?usp=sharing

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

Thanks!
David Sabeti
Project Lead, CF Release Integration

Awesome!!!

Super excited about moving all of cf forward on to cf-deployment!

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?
Thanks.

/Benjamin (depuis mon iPhone)



Bien cordialement,
/Benjamin Gandon (depuis mon iPhone)

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
<https://www.pivotaltracker.com/story/show/143199685> 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.

David

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

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?
Thanks.

/Benjamin (depuis mon iPhone)



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

Hi cf-dev,

As cf-deployment <https://github.com/cloudfoundry/cf-deployment> moves
closer to general availability (GA), we want to propose a schedule for
deprecating cf-release <https://github.com/cloudfoundry/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:


https://docs.google.com/document/d/1KLl4UIQbl92SvYom4fO-LcEoMK1D45KmjA988MwnOR4/edit?usp=sharing

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

Thanks!
David Sabeti
Project Lead, CF Release Integration

Hi David,

From talking to our teams here locally, one point that is important for us to have the same out of the box IaaS coverage than what we have in cf-release today (for us, specifically this means OpenStack, AWS, Azure, Google Cloud).

Not sure if this is already considered in the current planning and it’s also two days after your deadline, but I have the feeling it’s better to raise this as an input from our end before a GA announcement is made.

Thanks in advance,
Bernd

Bernd Krannich
SAP Cloud Platform
SAP SE
Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany

Pflichtangaben/Mandatory Disclosure Statement: www.sap.com/impressum<http://www.sap.com/company/legal/impressum.epx/>

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.


From: David Sabeti <dsabeti(a)pivotal.io>
Reply-To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org>
Date: Saturday, 24. June 2017 at 00:56
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org>
Subject: [cf-dev] Re: Re: Proposal: Plan to Deprecate cf-release

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<https://www.pivotaltracker.com/story/show/143199685> 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.

David

Hi Bernd,

Thanks for the feedback. I responded to your comment in the doc. Let me
know there what you think.

David

On Wed, Jul 5, 2017 at 6:20 AM Krannich, Bernd <bernd.krannich(a)sap.com>
wrote:

Hi David,



From talking to our teams here locally, one point that is important for us
to have the same out of the box IaaS coverage than what we have in
cf-release today (for us, specifically this means OpenStack, AWS, Azure,
Google Cloud).



Not sure if this is already considered in the current planning and it’s
also two days after your deadline, but I have the feeling it’s better to
raise this as an input from our end before a GA announcement is made.



Thanks in advance,

Bernd



*Bernd Krannich*

SAP Cloud Platform

*SAP SE*

Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany



Pflichtangaben/Mandatory Disclosure Statement: www.sap.com/impressum
<http://www.sap.com/company/legal/impressum.epx/>



Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige
vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich
erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine
Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte
benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen
Dank.



This e-mail may contain trade secrets or privileged, undisclosed, or
otherwise confidential information. If you have received this e-mail in
error, you are hereby notified that any review, copying, or distribution of
it is strictly prohibited. Please inform us immediately and destroy the
original transmittal. Thank you for your cooperation.





*From: *David Sabeti <dsabeti(a)pivotal.io>
*Reply-To: *"Discussions about Cloud Foundry projects and the system
overall." <cf-dev(a)lists.cloudfoundry.org>
*Date: *Saturday, 24. June 2017 at 00:56
*To: *"Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>
*Subject: *[cf-dev] Re: Re: Proposal: Plan to Deprecate cf-release



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
<https://www.pivotaltracker.com/story/show/143199685> 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.



David



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

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?

Thanks.

/Benjamin (depuis mon iPhone)





Bien cordialement,

/Benjamin Gandon (depuis mon iPhone)

Le 23 juin 2017 à 01:55, David Sabeti <dsabeti(a)pivotal.io> a écrit :

Hi cf-dev,



As cf-deployment <https://github.com/cloudfoundry/cf-deployment> moves
closer to general availability (GA), we want to propose a schedule for
deprecating cf-release <https://github.com/cloudfoundry/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:




https://docs.google.com/document/d/1KLl4UIQbl92SvYom4fO-LcEoMK1D45KmjA988MwnOR4/edit?usp=sharing



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



Thanks!

David Sabeti

Project Lead, CF Release Integration