CF v265

[ghost]

cf-release Release Candidate SHA for v265: 0d56d84d39a60af62ba83a6746845fc231c17f53

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: Updated nats to nats-release v18

---

@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: No changes to consul-release/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:

---

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

• Approval: :+1:
• Decider: @shashwathi
• Comments: No changes to routing release

---

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

• Approval: :+1:
• Decider: @plfx
• 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: 👍
• Decider: @ahevenor
• Comments:
  • Loggregator 89
  • statsd 1.0.25

---

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

---

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

---

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

---

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

• Approval: :+1:
• Decider: @ematpl
• Comments: Diego 1.19.0 / GR 1.8.0 / cflinuxfs2 1.133.0 / cf-networking 1.1.0 are compatible.

---

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

• Approval: :+1:
• Decider: @dsabeti via @mcwumbly
• Comments: cf-networking 1.1.0

---

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

• Approval: :+1:
• Decider: @glestaris
• Comments: v0.20.0 is compatible with Garden runC 1.8.0 and Diego 1.19.0.

[dsabeti]

$ git push origin 0d56d84d39a60af62ba83a6746845fc231c17f53:release-elect

[dsabeti]

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