correct. v213 is fine for new deployments. it is not possible to upgrade to
v213 with zero-downtime to the cloud controllers from a previous release,
which is the reason for the note.

On Fri, Jul 17, 2015 at 2:48 AM, Prysmakou Aliaksandr <
aliaksandr.prysmakou(a)altoros.com> wrote:

@Alex Lomov,

AFAIK it v213 is OK for fresh deployments.

Alex Prysmakou / Altoros
Tel: (617) 841-2121 ext. 5161 | Toll free: 855-ALTOROS
Skype: aliaksandr.prysmakou
www.altoros.com | blog.altoros.com | twitter.com/altoros

On Jul 17, 2015, at 12:34 PM, Alex Lomov <alexander.lomov(a)altoros.com>
wrote:

I don’t think that v213 is suitable cf-release for you. It was a notice
about its fails [1].

My colleagues are playing around v212, and I have rather stable
deployment of v207.

[1] http://lists.cloudfoundry.org/pipermail/cf-dev/2015-July/000702.html


On Jul 2, 2015, at 10:11 PM, Tim Dunphy <bluethundr(a)gmail.com> wrote:

Hey guys,

I was thinking of setting up open source CF on AWS. The only constraint
is that it has to work within the free tier.

What version of open source CF would you recommend I use?

Thanks,
Tim
--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh



_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Thank you,

James Bayer