CF v273

[ghost]

cf-release Release Candidate SHA for v273: 0b5280310d531d02a07335eb1de7460e20118c19

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: / :-1:
• Decider:
• 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: etcd v104 (no change), consul v173 (no change)

---

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

---

@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 / 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: @bradylove
• 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:
• 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.5

---

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

• Approval: :+1:
• Decider: @emalm
• Comments: Diego 1.25.3 / GR 1.9.3 / cflinuxfs2 1.151.0 / cf-networking 1.6.0 / grootfs 0.25.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.25.0

[spikymonkey]

Hi @dsabeti, please could you replace me (@spikymonkey) with @tscolari as the GrootFS anchor for these notifications? We've rotated :)

[ghost]

cf-release Release Candidate SHA for v273: e4d5f0e67e071efdddc1556030d008733f67c5e6

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: @dsabeti
• Comments: No change since the last proposed RC, which was approved.

---

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

---

@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 / 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 95 statsd-1.0.30

---

@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.41.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: @dsabeti
• Comments: No change since the last proposed RC, which was approved

---

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

---

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

• Approval: :+1:
• Decider: @emalm
• Comments: Diego 1.25.3 / GR 1.9.3 / cflinuxfs2 1.154.0 / cf-networking 1.6.0 / grootfs 0.25.0 are compatible.

---

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

• Approval: :+1:
• Decider: @rusha19
• Comments: v1.6.0

---

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

• Approval: :+1:
• Decider: @glestaris
• Comments: v0.25.0

[dsabeti]

$ git push origin e4d5f0e67e071efdddc1556030d008733f67c5e6:release-elect

[dsabeti]

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