Re: Cloud Foundry final release selection process now public


john mcteague <john.mcteague@...>
 

More transparency is always welcome, nice to see it public.

On Tue, Feb 9, 2016 at 9:56 PM, Chip Childers <cchilders(a)cloudfoundry.org>
wrote:

Great work Amit and the whole Release Integration team. It's awesome to
have this public now!

Chip Childers | VP Technology | Cloud Foundry Foundation

On Tue, Feb 9, 2016 at 4:02 PM, Amit Gupta <agupta(a)pivotal.io> wrote:

Hey cf-dev,

I'm pleased to announce that the process by which final releases of Cloud
Foundry are selected is now public.

The cf-final-release-election repo [1] contains GitHub issues for each
release candidate, and the project leads for each core component are asked
to approve or disapprove a given candidate SHA for promotion. The
community now has visibility into this election process.

For the curious, here's a little more info about what happens before a
SHA is announced as a release candidate, and what happens after a given SHA
is approved for promotion to actually cut a final release.

Beforehand, a SHA of cf-release works its way through the cf-release
pipeline [2], which leads to the promotion of a SHA of the cf-release repo
to its release-candidate branch. We have a longer term goal to make the
full build outputs of the jobs in these pipelines also publicly viewable.

Similarly, the diego pipeline [3] vets a SHA of diego-release, and final
release of garden-linux-release and etcd-release. One of the jobs in this
pipeline is to deploy and test into an environment that is shared with the
cf-release pipeline, to truly certify integration compatibility.

SHAs of cf-release are being promoted to the release-candidate branch
continuously, and roughly once a week we announce one such SHA for the
project leads to elect via the announce-rc job [4]. If all leads approve,
the SHA is promoted to the release-elect branch of cf-release, which
automatically triggers the building of a final release via the
create-final-release [5] job.

We are continuously working on making these processes more discoverable
and transparent to the community.

[1] https://github.com/cloudfoundry/cf-final-release-election
[2] https://runtime.ci.cf-app.com/pipelines/cf-release?groups=cf-release
[3] https://diego.ci.cf-app.com/pipelines/main?groups=diego
[4] https://mega.ci.cf-app.com/pipelines/release/jobs/announce-rc
[5]
https://mega.ci.cf-app.com/pipelines/cf-release/jobs/create-final-release

Cheers,

Amit Gupta
CF Release Integration team PM, Pivotal

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.