CF v260

[ghost]

cf-release Release Candidate SHA for v260: 9619c26586d19ebd8a96c9eb88b8e130567bda2e

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

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

---

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

---

@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: / :-1:
• Decider:
• Comments:

---

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

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

---

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

• Approval: :+1: / :-1:
• Decider:
• 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: :+1:
• Decider: @ahevenor
• Comments: Loggregator 86 statsd-injector-release 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:

---

@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: / :-1:
• Decider:
• 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.16

---

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

• Approval: :-1:
• Decider: @ematpl
• Comments: The only compatible Diego release listed is v1.15.1, which is not recommended for production use.

---

@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: / :-1:
• Decider:
• Comments:

[emalm]

@dsabeti 👎 to https://github.com/cloudfoundry/cf-release/commit/9619c26586d19ebd8a96c9eb88b8e130567bda2e, but I would like to propose instead the newly promoted https://github.com/cloudfoundry/cf-release/commit/1216951fc69e13399e430bc1e2ccf9d78b210f5d.

[ghost]

cf-release Release Candidate SHA for v260: 1216951fc69e13399e430bc1e2ccf9d78b210f5d

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

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

---

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

• Approval: :+1:
• Decider: @evanfarrar
• 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: :+1: / :-1:
• Decider:
• 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: Routing will address the bug introduced in routing release 0.153.0 in next release.

---

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

• Approval: :+1: / :-1:
• Decider:
• 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: :+1: / :-1:
• Decider:
• Comments:

---

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

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

---

@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: / :-1:
• Decider:
• 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: / :-1:
• Decider:
• Comments:

---

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

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

---

@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: / :-1:
• Decider:
• Comments:

[shashwathi]

@dsabeti : We are close to cutting a release with the bug fix. Can we hold this release until then?

Regards Shash

[dsabeti]

@shashwathi Sounds good.

[shashwathi]

@dsabeti : Proposing the sha 8af4d733a35e685b3aeafba19fc34bc2e6fb271b

[ghost]

cf-release Release Candidate SHA for v260: b07978a2a888df192bdc510b958d8bb09b026006

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

• Approval: :+1: / :-1:
• Decider:
• 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: :-1:
• Decider: @valeriap
• Comments: working on upgrade to PostgreSQL 9.6.3. Can we wait for it?

---

@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: Routing release bumped to v0.154.0

---

@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: :+1:
• Decider: @jasonkeene
• Comments: Loggregator v87 statsd Injector v1.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:

---

@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: / :-1:
• Decider:
• 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.16

---

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

• Approval: :+1:
• Decider: @ematpl
• Comments: Diego 1.15.3 / GR 1.7.0 / cflinuxfs2 1.119.0 / cf-networking 0.23.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: / :-1:
• Decider:
• Comments:

[valeriap]

@dsabeti postgres-release v17 bumped with commit 1e0e0f31404def7dd1ef29740b66a69b21fe1eb2

[ghost]

cf-release Release Candidate SHA for v260: 1e0e0f31404def7dd1ef29740b66a69b21fe1eb2

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.

---

@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: Simon
• Comments: SHA is current

---

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

---

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

• Approval: :+1:
• Decider: @jaydunk
• Comments:

---

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

• Approval: :+1:
• Decider: @glestaris
• Comments: v0.18.0 is compatible with Garden runC v1.6.0. We do not expect any issues with Garden runC v1.7.0 given the Garden runC's release notes.

[dgodd]

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

Approval: 👍 Decider: dgodd Comments: Go buildpack has a bug which has since been fixed. But previous cf-release had the same bug.

[plfx]

We have an important fix to include. @dsabeti

Can we move to proposal to f9ceec382ed1f891a96f494194d73836181fab04

[ghost]

cf-release Release Candidate SHA for v260: 6247d0e4c0595418cca2b015dd3151efa251b396

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

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

---

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

• Approval: :+1: / :-1:
• Decider:
• 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: :+1: / :-1:
• Decider:
• Comments:

---

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

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

---

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

• Approval: :+1: / :-1:
• Decider:
• 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: :+1: / :-1:
• Decider:
• Comments:

---

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

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

---

@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: / :-1:
• Decider:
• 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: / :-1:
• Decider:
• Comments:

---

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

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

---

@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: / :-1:
• Decider:
• Comments:

[dsabeti]

$ git push origin 6247d0e4c0595418cca2b015dd3151efa251b396:release-elect

[dsabeti]

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