CF v249

[ghost]

cf-release Release Candidate SHA for v249: d86b0fd3cb4723ef0edea8a7eb3c08cb1cca2980

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: / :-1:
• Decider:
• Comments:

---

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

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

---

@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: / :-1:
• Decider:
• Comments:

---

@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: / :-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 & @jasonkeene
• Comments: Includes updated cipher suites and minimum TLS Version

---

@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: / :-1:
• Decider:
• Comments:

---

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

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

---

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

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

[dsabeti]

We need to move forward with cutting the release. Feel free to leave any comments here regarding the candidate SHA. If there's any issue with this release, we can do a fast follow.

[dsabeti]

Cutting the release: git push origin d86b0fd3cb4723ef0edea8a7eb3c08cb1cca2980:release-elect

[dsabeti]

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