search

cloudfoundry-attic / cf-final-release-election

4 stars 1 forks source link

CF v248 #20

Closed ghost closed 7 years ago

ghost commented 7 years ago

cf-release Release Candidate SHA for v248: b1b3c228fc1ebd0fdf3b1a9d6d3a866eaf273651

Please read these instructions, as they changed on 4 Nov 2015.

@dsabeti, @JesseTAlford: Does this cf-release SHA look good for the release integration team? Any bugs, regressions, or incomplete features of concern?

@zankich, @christianang: Does this cf-release SHA look good for the infrastructure team? Any bugs, regressions, or incomplete features of concern?

@valeriap, @smoser-ibm: Does this cf-release SHA look good for the postgres-release team? Any bugs, regressions, or incomplete features of concern?

@shalako, @shashwathi: Does this cf-release SHA look good for the routing team? Any bugs, regressions, or incomplete features of concern?

@sreetummidi, @plfx: Does this cf-release SHA look good for the identity team? Any bugs, regressions, or incomplete features of concern?

@ahevenor, @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?

@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?

@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?

emalm commented 7 years ago

@dsabeti @JesseTAlford maybe we should nix the b1b3c22 candidate because the BOSH-Lite template is broken (no END RSA PRIVATE KEY PEM boundary line at https://github.com/cloudfoundry/cf-release/blob/b1b3c228fc1ebd0fdf3b1a9d6d3a866eaf273651/templates/cf-infrastructure-bosh-lite.yml#L844-L845, as reported in https://github.com/cloudfoundry/cf-release/issues/1111)?

sreetummidi commented 7 years ago

@dsabeti @plfx will take care of it

dsabeti commented 7 years ago

@sreetummidi @plfx @ematpl

I'll propose a new candidate once the change makes it through our pipeline.

sreetummidi commented 7 years ago

Sounds good !

ghost commented 7 years ago

cf-release Release Candidate SHA for v248: 4e1caa3492ee7b618dedc80fa9a3241a99a41e0f

Please read these instructions, as they changed on 4 Nov 2015.

@dsabeti, @JesseTAlford: Does this cf-release SHA look good for the release integration team? Any bugs, regressions, or incomplete features of concern?

@zankich, @christianang: Does this cf-release SHA look good for the infrastructure team? Any bugs, regressions, or incomplete features of concern?

@valeriap, @smoser-ibm: Does this cf-release SHA look good for the postgres-release team? Any bugs, regressions, or incomplete features of concern?

@shalako, @shashwathi: Does this cf-release SHA look good for the routing team? Any bugs, regressions, or incomplete features of concern?

@sreetummidi, @plfx: Does this cf-release SHA look good for the identity team? Any bugs, regressions, or incomplete features of concern?

@ahevenor, @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?

@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?

@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?

dsabeti commented 7 years ago

Cutting final release: git push origin 4e1caa3492ee7b618dedc80fa9a3241a99a41e0f:release-elect

dsabeti commented 7 years ago

Final release is up on bosh.io: http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=248