CF v242

[ghost]

cf-release Release Candidate SHA for v242: bd6fa28b15a9118d9954e40f3d2af5603a16ac11

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.

---

@Amit-PivotalLabs, @JesseTAlford, @dsabeti: Does this cf-release SHA look good for the release integration team? Any bugs, regressions, or incomplete features of concern?

• Approval: :+1:
• Decider: @Amit-PivotalLabs
• Comments: bumped nats-release from v8 to v11, introducing links for user, password, port (and implicitly machines), including adding default: 4222 to nats.port property

---

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

• Approval: :+1:
• Decider: @Amit-PivotalLabs
• Comments: bumped consul-release from v108 to v110, with no major functional changes, but several implementation changes from PR to support consul_agent on BOSH Windows stemcells.

---

@Amit-PivotalLabs, @valeriap: Does this cf-release SHA look good for the postgres-release team? Any bugs, regressions, or incomplete features of concern?

• Approval: :+1:
• Decider: @Amit-PivotalLabs
• Comments: No changes.

---

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

• Approval: 👍
• Decider: @shashwathi
• Comments: No changes.

---

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

• Approval: :+1:
• Decider: Sree T.
• Comments: Updated to UAA 3.7.0

---

@AllenDuet, @wfernandes: 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: @wfernandes
• Comments: dea_logging_agent has been made a submodule for easier removal from Loggregator in the future.

---

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

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

---

@sclevine, @RochesterinNYC: 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.8.1

---

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

• Approval: :+1:
• Decider: @ematpl
• Comments: Diego 0.1485.0 / GL 0.342.0 / etcd 67 / cflinuxfs2 1.29.0 are compatible.

---

@fraenkel, @sykesm: Does this cf-release SHA look good for the DEA + HM9000 team? Any bugs, regressions, or incomplete features of concern?

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

[SocalNick]

Last, sorry for the delay, CAPI is in an inception.

[Amit-PivotalLabs]

$ git push origin bd6fa28b15a9118d9954e40f3d2af5603a16ac11:release-elect
Total 0 (delta 0), reused 0 (delta 0)
To git@github.com:cloudfoundry/cf-release
   638c22f..bd6fa28  bd6fa28b15a9118d9954e40f3d2af5603a16ac11 -> release-elect

[Amit-PivotalLabs]

Concourse builds, GitHub repo, and bosh.io release all look good.