CF v246

[ghost]

cf-release Release Candidate SHA for v246: 81ed088c0983c90321ab5fffc1d90acf867385ea

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

• Edit this comment by setting the approval for your section (delete the thumb you don't want)
• Also set your GitHub handle as the approver
• Add any additional comments you may have in your section
• If you notice you are the last person to set your approval, as a courtesy please also add a new comment to the issue saying so, so that we get GitHub notifications that all approvals are done.

---

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

• Approval: :+1:
• Decider: @Amit-PivotalLabs
• Comments: Bump nats-release from v11 to v14: send service logs to syslog [details]; bump from golang 1.6.3 to 1.7 [details].

---

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

• Approval: :+1:
• Decider: @Amit-PivotalLabs
• Comments: Bump consul-release from v126 to v128: Fix issue with drain logic so that it doesn't happen on clients [details]; initial support for consul_agent_windows; retry leader status check when starting in bootstrap, improving stability [details]. Bump etcd-release from v73 to v77: Switch etcd.disable_network_diagnostics (default false) to etcd.enable_network_diagnostics (default true) [details]; Add etcd.network_diagnostics_duration_in_seconds (default 300) so that sidecar doesn't fill up logs [details]; Fix issue with sidecar failing to stop [details]; Fix how sidecar works in SSL mode [details]

---

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

• Approval: :+1:
• Decider: @valeriap
• Comments: No changes

---

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

• Approval: :+1: / :-1:
• Decider:
• Comments:

---

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

• Approval: :-1:
• Decider: @plfx
• Comments: uaa-release needs to be bumped to v20 for some fixes that PivNet is depending on. We are re-running our pipeline with the other module bumps.

---

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

• Approval: :+1:
• Decider: @wfernandes
• Comments: No Changes

---

@SocalNick, @utako: Does this cf-release SHA look good for the CAPI team? Any bugs, regressions, or incomplete features of concern?

• Approval: :+1: / :-1:
• Decider:
• Comments:

---

@sclevine, @RochesterinNYC: Does this cf-release SHA look good for the Buildpacks and Stacks team? Any bugs, regressions, or incomplete features of concern?

• Approval: :+1: / :-1:
• Decider:
• Comments:

---

@nebhale, @cgfrost: Does this cf-release SHA look good for the Java Buildpack team? Any bugs, regressions, or incomplete features of concern?

• Approval: :+1:
• Decider: @nebhale
• Comments: v3.9

---

@ematpl, @jfmyers9: Can you provide a compatible diego-release SHA?

• Approval: :+1:
• Decider: @ematpl
• Comments: Diego 0.1487.0 / GR 1.0.0 / etcd 77 / cflinuxfs2 1.36.0 are compatible.

---

@fraenkel, @sykesm: Does this cf-release SHA look good for the DEA + HM9000 team? Any bugs, regressions, or incomplete features of concern?

• Approval: :+1:
• Decider: @fraenkel
• Comments:

[plfx]

Thumbed down. The pipeline is currently chewing on the version that we need to bump to.

[fraenkel]

Where are we on this?

[dsabeti]

Hey @fraenkel, thanks for checking in. We're currently working our way through a broken pipeline. As soon as it gets fixed, I'll propose a new commit.

[ghost]

cf-release Release Candidate SHA for v246: e49436ed475f391ebff422b391d89856140ae920

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

• Edit this comment by setting the approval for your section (delete the thumb you don't want)
• Also set your GitHub handle as the approver
• Add any additional comments you may have in your section
• If you notice you are the last person to set your approval, as a courtesy please also add a new comment to the issue saying so, so that we get GitHub notifications that all approvals are done.

---

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

• Approval: :+1:
• Decider: @dsabeti
• Comments:

---

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

• Approval: :+1:
• Decider: @zankich
• Comments:
  • consul-release has been bumped to v133
  • etcd-release has been bumped to v77

---

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

• Approval: :+1:
• Decider:@smoser
• Comments:

---

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

• Approval: :+1:
• Decider: Shannon
• Comments: routing-release has been bumped to 0.141.0

---

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

• Approval: :+1:
• Decider: Sree T.
• Comments: Updated to UAA 3.8.0

---

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

• Approval: :+1:
• Decider: @wfernandes
• Comments: No Changes.

---

@SocalNick, @utako: Does this cf-release SHA look good for the CAPI team? Any bugs, regressions, or incomplete features of concern?

• Approval: :+1:
• Decider: @SocalNick
• Comments:

---

@sclevine, @RochesterinNYC: Does this cf-release SHA look good for the Buildpacks and Stacks team? Any bugs, regressions, or incomplete features of concern?

• Approval: :+1:
• Decider: @sclevine
• Comments: There are a number of medium CVEs in cflinuxfs2 that haven't made it to cf-release yet. Probably nothing worth holding up the release. Also, the .Net Core buildpack has not yet been integrated (https://github.com/cloudfoundry/cf-release/pull/1084).

---

@nebhale, @cgfrost: Does this cf-release SHA look good for the Java Buildpack team? Any bugs, regressions, or incomplete features of concern?

• Approval: :+1:
• Decider: @nebhale
• Comments: v3.10

---

@ematpl, @jfmyers9: Can you provide a compatible diego-release SHA?

• Approval: :+1:
• Decider: @ematpl
• Comments: Diego 0.1487.0 / GR 1.0.0 / etcd 78 / cflinuxfs2 1.38.0 are compatible.

---

@fraenkel, @sykesm: Does this cf-release SHA look good for the DEA + HM9000 team? Any bugs, regressions, or incomplete features of concern?

• Approval: :+1:
• Decider: @fraenkel
• Comments:

[sclevine]

Python and PHP buildpacks in this commit may be vulnerable to a high memcached CVE. I don't think we should hold up the release for this, as I can instruct users of v246 to upgrade those buildpacks in the release notes.

@dsabeti

[dsabeti]

Thanks for the update @sclevine.

Otherwise, it looks like everybody else has approved the SHA, so we're moving on this now.

git push origin e49436ed475f391ebff422b391d89856140ae920:release-elect

[dsabeti]

Final release on bosh.io: http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=246 Final release on cf-release master: https://github.com/cloudfoundry/cf-release/commit/fa428609f711cceae2a606ce61e059d4009b5602