Re: Release Notes for v210
|
Hi,
toggle quoted message
Show quoted text
Thanks for the v210 announcement and the associated release note. It seems that the v209-announced introduction of a new mandatory metron_agent.deployment property did not make it into the default spiff templates [5]. Note I tried updating v209 release note formatting to make this more explicit [6]. I'm wondering whether the pivotal runtime/release team has a cf-release pipeline for vsphere infrastructure (I'm suspecting the aws-based pipelines were fine) ? Is such pipeline using the spiff templates into cf-release/templates [4], or has it moved to something else such as cf-boshworkspace [3] ? If the spiff templates templates into cfrelease/templates are still the recommended way of deploying CF, is there a way to priorize the merge of PRs for known issues in v211 such as [1] and [2], as to avoid the need by the cf-community to maintain its own fork of cfrelease/templates ? Thanks in advance, Guillaume. [1] https://github.com/cloudfoundry/cf-release/pull/689 [2] https://github.com/cloudfoundry/cf-release/pull/696 [3] https://github.com/cloudfoundry-community/cf-boshworkspace [4] https://github.com/cloudfoundry/cf-release/tree/master/templates [5] https://github.com/cloudfoundry/cf-release/issues/690 [6] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki/v209/fdae17795c61691f96f90cc9fd7be90945252937
On Wed, May 27, 2015 at 7:59 AM, Dieu Cao <dcao(a)pivotal.io> wrote:
The cf-release v210 was released on May 23rd, 2015 |
|
|