CF v257

[ghost]

cf-release Release Candidate SHA for v257: 2214fd2618fe36c7d3acbe5954e6f5a217bf042e

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, @anEXPer: 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:

---

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

• Approval: :+1:
• Decider: @christianang
• Comments: Bumped etcd-release to v100. Added BOSH links to etcd-release.

---

@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: @valeriap
• Comments: v16

---

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

---

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

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

---

@ahevenor, @jasonkeene: 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: @ahevenor
• Comments: Loggregator 84 statsd 1.0.22

---

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

• Approval: :+1:
• Decider: zach
• Comments:

---

@sclevine, @dgodd: 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: Worried that the Diego rootfs (1.60.0) continues to fall behind the DEA rootfs (1.113.0). No high CVEs yet though.

---

@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.15

---

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

• Approval: :+1:
• Decider: @ematpl
• Comments: Diego 1.13.0 / GR 1.5.0 / cflinuxfs2 1.60.0 / cf-networking 0.20.0 are compatible.

---

@rusha19, @jaydunk: Can you provide a compatible cf-networking-release SHA or final release version?

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

---

@glestaris, @spikeymonkey: Can you provide a compatible grootfs-release SHA or final release version?

• Approval: :+1:
• Decider: @glestaris
• Comments: v0.17.0.

[ghost]

cf-release Release Candidate SHA for v257: f7a37811328cd6c6af61a4ad8372c41056f3e728

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.

---

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

• Approval: :+1:
• Decider: @christianang
• 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: Sree T.
• Comments: Updated to v30 aka UAA 3.15.0

---

@rusha19, @jaydunk: Can you provide a compatible cf-networking-release SHA or final release version?

• Approval: :+1:
• Decider: @rusha19
• Comments: v0.20.0

[dsabeti]

Hi all. We needed to get a new release candidate in order to ship a CVE fix. I've removed everybody from the update whose releases haven't changed since they gave a thumbs up in the initial proposed RC.

[dsabeti]

Cutting release: $ git push origin f7a37811328cd6c6af61a4ad8372c41056f3e728:release-elect

[dsabeti]

Release is published: https://github.com/cloudfoundry/cf-release/releases/tag/v257 http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=257