Closed ghost closed 8 years ago
$ git push origin 638c22f9eae6727df7d78fb44bb3348a9b5d7967:release-elect
Total 0 (delta 0), reused 0 (delta 0)
To git@github.com:cloudfoundry/cf-release.git
cf65a6e..638c22f 638c22f9eae6727df7d78fb44bb3348a9b5d7967 -> release-elect
cf-release Release Candidate SHA for v241: 638c22f9eae6727df7d78fb44bb3348a9b5d7967
Please read these instructions, as they changed on 4 Nov 2015.
@Amit-PivotalLabs, @JesseTAlford: Does this cf-release SHA look good for the release integration team? Any bugs, regressions, or incomplete features of concern?
@Amit-PivotalLabs, @zankich: Does this cf-release SHA look good for the infrastructure team? Any bugs, regressions, or incomplete features of concern?
@Amit-PivotalLabs, @valeriap: Does this cf-release SHA look good for the postgres-release team? Any bugs, regressions, or incomplete features of concern?
@shalako, @crhino: Does this cf-release SHA look good for the routing team? Any bugs, regressions, or incomplete features of concern?
@sreetummidi, @mbhave: Does this cf-release SHA look good for the identity team? Any bugs, regressions, or incomplete features of concern?
@AllenDuet, @wfernandes: Does this cf-release SHA look good for the Loggregator team? Do the a1 logging metrics look nominal? Any bugs, regressions, or incomplete features of concern?
metron_agent_windows
job to loggregator release@SocalNick, @utako: Does this cf-release SHA look good for the CAPI team? Any bugs, regressions, or incomplete features of concern?
@sclevine, @RochesterinNYC: Does this cf-release SHA look good for the Buildpacks and Stacks team? Any bugs, regressions, or incomplete features of concern?
@nebhale, @cgfrost: Does this cf-release SHA look good for the Java Buildpack team? Any bugs, regressions, or incomplete features of concern?
v3.8.1
@ematpl, @jfmyers9: Can you provide a compatible diego-release SHA?
@fraenkel, @sykesm: Does this cf-release SHA look good for the DEA + HM9000 team? Any bugs, regressions, or incomplete features of concern?