One more thing to add, we're also keeping an eye on the "cloudfoundry" tag
on StackOverflow, so feel free to ask questions there as well.

Best,
Amit

On Wed, Nov 25, 2015 at 8:04 PM, Amit Gupta <agupta(a)pivotal.io> wrote:

Hey all,

The CF Release Integration team (also known as "MEGA") will be splitting
into two smaller teams. The current team's responsibilities included:

- splitting out, maintaining, and adding features to an etcd-release
- splitting out, maintaining, and adding features to a consul-release
- splitting out and maintaining a NATS-release
- splitting out and maintaining a "pre-diego-runtime"-release (DEA,
Warden, HM9k)
- splitting out and maintaining a postgres-release
- owning the CATS and cf-smoke-tests
- managing the main integration pipelines that take all the bits and
create a usable, well-tested distribution of the CF components
- managing the cf-release repo, and the final release process
- building tooling to generate manifests that compose all the split-out
releases
- building tooling to automate bootstrapping environments for Concourse
and CF (no more snowflakes)
- canary apps used to monitor integration and production environments
- providing other common functionality, e.g. route registration

This is a lot of context for a small team of two pairs to juggle, and it
could arguably be the work of several teams, but we will start with two
one-pair teams for now.

*CF Release Integration* (no longer referred to as MEGA?)
- splitting out and maintaining a "pre-diego-runtime"-release (DEA,
Warden, HM9k)
- owning the CATS and cf-smoke-tests
- managing the main integration pipelines that take all the bits and
create a usable, well-tested distribution of the CF components
- managing the cf-release repo, and the final release process
- building tooling to generate manifests that compose all the split-out
releases
- canary apps used to monitor integration and production environments
- providing other common functionality, e.g. route registration

Product Manager: Amit Gupta, Pivotal
Lead Engineer: Rob Dimsdale, Pivotal
Engineer: Zachary Auerbach, Pivotal

*CF Infrastructure*
- splitting out, maintaining, and adding features to an etcd-release
- splitting out, maintaining, and adding features to a consul-release
- splitting out and maintaining a NATS-release
- splitting out and maintaining a postgres-release
- building tooling to generate manifests that compose all the split-out
releases

Product Manager: Amit Gupta, Pivotal
Lead Engineer: Ryan Moran, Pivotal
Engineer: Adrian Zankich, Pivotal

We look forward to collaborating with all of you, we're still on the
usual communication channels -- the cf-dev mailing list, and issues and PR
on GitHub -- no changes there!

Cheers,
Amit