Spike: Should the Pipelines and Tools teams be included in this epic

The Edge team recently completed an epic to create pipelines for all of the subcomponents that comprise the BBE solution. These pipelines were created by the Edge team but follow similar patterns as the main Big Bang pipelines and live inside of the Pipeline Templates repo.

Part of the release process epic is to create tooling and update pipelines to match and support the separate release process for BBE. If the Edge team owns those tasks and code, then we're effectively our own Pipeline and Tools teams in addition to the responsibilities over the Edge code.

It's worth discussing whether it would be possible to have the Pipeline and Tools teams participate alongside the Edge team on this instead. That has a lot of benefits, including:

• A dedicated Pipeline team could either reuse or create new standardized code for the Edge pipelines. We attempted to leverage what we could from the existing pipelines, but are not as familiar with that code.
• The Tools team has deep knowledge of the current release process and the R2D2 tool automation supporting it. On the other hand, no one on the Edge team has done a Big Bang release or used R2D2 so finding common ground or reusable code would be challenging.
• Allows the Edge team to focus more on its core responsibility: the BBE solution.