CF v281

[ghost]

cf-release Release Candidate SHA for v281: e6d853bf7e0260c39efff1600fe4302bfbdff05f

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

---

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

---

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

• Approval: :+1:
• Decider: @aaronshurley
• Comments: v0.167.0

---

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

• Approval: :+1:
• Decider: @jhamon
• Comments: v52.4

---

@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: @ahevenor
• 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.45.0 no change

---

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

• Approval: :+1:
• Decider: @dsabeti
• 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.6

---

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

• Approval: :+1:
• Decider: @emalm
• Comments: Diego 1.30.0 / GR 1.10.0 / cflinuxfs2 1.170.0 / cf-networking 1.8.1 / grootfs 0.30.0 are compatible.

---

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

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

[dsabeti]

$ git push origin e6d853bf7e0260c39efff1600fe4302bfbdff05f:release-elect

[dsabeti]

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