CF v243

[ghost]

cf-release Release Candidate SHA for v243: ee7d00886397fa9d1ee0f3aa9d3b1c236a077336

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: No changes.

---

@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: No changes.

---

@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: @Amit-PivotalLabs
• 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:
• Decider: Shannon
• Comments: routing-release bumped to 0.138.0

---

@sreetummidi, @mbhave: 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: Bumped to V17 (UAA 3.7.3)

---

@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 since v242

---

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

---

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

---

@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.1485.0 / GL 0.342.0 / etcd 67 / cflinuxfs2 1.29.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: no changes

[emalm]

@Amit-PivotalLabs As of yesterday afternoon, everyone had signed off with a 👍 .

[Amit-PivotalLabs]

$ git push origin ee7d00886397fa9d1ee0f3aa9d3b1c236a077336:release-elect
Total 0 (delta 0), reused 0 (delta 0)
To git@github.com:cloudfoundry/cf-release
   bd6fa28..ee7d008  ee7d00886397fa9d1ee0f3aa9d3b1c236a077336 -> release-elect

[Amit-PivotalLabs]

Final release build in progress.

[Amit-PivotalLabs]

• Final release on master branch of cf-release repo: https://github.com/cloudfoundry/cf-release/commit/dbdf0b46d9182bc1342b305162ea49045f624b13
• Final release on bosh.io: http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=243