CF v270

[ghost]

cf-release Release Candidate SHA for v270: bf2e945ecfa09734c3cd8a6c9989b136807e3659

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: @genevievelesperance
• 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: 👍 :
• Decider: @smoser-ibm
• Comments: no change, same as 269

---

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

---

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

---

@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
• Comments: Loggregator 92 stats d 1.0.29

---

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

---

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

---

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

• Approval: :+1:
• Decider: @ematpl
• Comments: Diego 1.23.2 / GR 1.9.0 / cflinuxfs2 1.145.0 / cf-networking 1.3.3 / grootfs 0.24.0 are compatible.

---

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

• Approval: :+1:
• Decider: @rusha19
• Comments: cf-networking 1.3.3

---

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

• Approval: :+1:
• Decider: @glestaris
• Comments: v0.24.0. Warning: GrootFS v0.24.0+ requires deploying Cloud Foundry with a recent BOSH CLI (BOSH CLI v2 or BOSH CLI v1.3262.26.0+).

[zrob]

@dsabeti turns out there's a pretty gnarly migration in this capi-release, we'll have to hold off on this :(

[ghost]

cf-release Release Candidate SHA for v270: 86d5a4f4cabc9e46d5c8864cfd6e95880295bc7d

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: v171 of consul is along for the ride with this SHA

---

@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: @smoser-ibm
• Comments: same as above

---

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

---

@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
• Comments: Loggregator 92 stats d 1.0.29

---

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

---

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

---

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

• Approval: :+1:
• Decider: @ematpl
• Comments: Diego 1.23.2 / GR 1.9.0 / cflinuxfs2 1.145.0 / cf-networking 1.3.3 / grootfs 0.24.0 are compatible.

---

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

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

---

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

• Approval: :+1:
• Decider: @glestaris
• Comments: v0.24.0. Warning: GrootFS v0.24.0+ requires deploying Cloud Foundry with a recent BOSH CLI (BOSH CLI v2 or BOSH CLI v1.3262.26.0+).

[dsabeti]

$ git push origin 86d5a4f4cabc9e46d5c8864cfd6e95880295bc7d:release-elect

[dsabeti]

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