ghost
commented
7 years ago cf-release Release Candidate SHA for v268: 4057a14022eef6d8810860094692fc9424540905
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 last proposed RC, which was approved.
@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: @dsabeti
- Comments: No change since last proposed RC, which was approved.
@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, @jhamon: 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: No Changes
@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 91 statsd 1.0.28
@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.35.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.18
@ematpl, @jvshahid: Can you provide a compatible diego-release SHA or final release version?
- Approval: :+1:
- Decider: @ematpl
- Comments: Diego 1.23.0 / GR 1.9.0 / cflinuxfs2 1.138.0 / cf-networking 1.2.0 / grootfs 0.21.0 are compatible.
@rusha19, @jaydunk: Can you provide a compatible cf-networking-release SHA or final release version?
- Approval: :+1:
- Decider: @jaydunk
- Comments:
v1.2.0
@glestaris, @spikymonkey: Can you provide a compatible grootfs-release SHA or final release version?
- Approval: :+1:
- Decider: @glestaris
- Comments: v0.21.0 is compatible with Diego v1.23.0 and Garden runC v1.9.0.
dsabeti
cf-release Release Candidate SHA for v268: 4f912743a5c71d6580a88aa2f0fa4a672dae0aa4
Please read these instructions, as they changed on 4 Nov 2015.
@dsabeti, @staylor14: Does this cf-release SHA look good for the release integration team? Any bugs, regressions, or incomplete features of concern?
@evanfarrar, @genevievelesperance: Does this cf-release SHA look good for the infrastructure team? Any bugs, regressions, or incomplete features of concern?
@valeriap, @smoser-ibm: Does this cf-release SHA look good for the postgres-release team? Any bugs, regressions, or incomplete features of concern?
@shalako, @shashwathi: Does this cf-release SHA look good for the routing team? Any bugs, regressions, or incomplete features of concern?
@sreetummidi, @jhamon: Does this cf-release SHA look good for the identity team? Any bugs, regressions, or incomplete features of concern?
@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?
@zrob, @gerg: Does this cf-release SHA look good for the CAPI team? Any bugs, regressions, or incomplete features of concern?
@sclevine, @dgodd: Does this cf-release SHA look good for the Buildpacks and Stacks team? Any bugs, regressions, or incomplete features of concern?
@nebhale: Does this cf-release SHA look good for the Java Buildpack team? Any bugs, regressions, or incomplete features of concern?
v3.18@ematpl, @jvshahid: Can you provide a compatible diego-release SHA or final release version?
@rusha19, @jaydunk: Can you provide a compatible cf-networking-release SHA or final release version?
@glestaris, @spikymonkey: Can you provide a compatible grootfs-release SHA or final release version?