CF v283

[ghost]

cf-release Release Candidate SHA for v283: bf7e70e88017dc2eac1211d021e7ade21cbdce5c

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, @staylor14: Does this cf-release SHA look good for the release integration team? Any bugs, regressions, or incomplete features of concern?

• Approval: :+1:
• Decider: @staylor
• Comments: FUSE test does not run successfully on VSphere. We suspect an issue with the Kernel introduced in the latest stemcell.

---

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

• Approval: :+1:
• Decider: @evanfarrar
• Comments: no changes

---

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

• Approval: :+1:
• Decider: @staylor
• Comments: no changes

---

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

• Approval: :+1:
• Decider: Shannon
• Comments: no change

---

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

• Approval: :+1:
• Decider: @staylor
• Comments: no changes

---

@ahevenor, @JohannaSmith: 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: @JohannaSmith
• Comments:

---

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

• Approval: :+1:
• Decider: @zrob
• Comments: 1.46.0

---

@sclevine: 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: 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: v4.7

---

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

• Approval: :+1:
• Decider: @staylor
• Comments: no changes

---

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

• Approval: :+1:
• Decider: @chinangela
• Comments: v1.8.1, no changes.

[staylor14]

git push origin bf7e70e8801:release-elect

[staylor14]

https://github.com/cloudfoundry/cf-release/releases/tag/v283