## Problem Statement So far in the Pipeline Stability track and in the MR Cycle Time project, we focused on **most merge request pipelines** and _some of_ the **default branch pipelines**. Optimizing for most of the merge requests pipelines might leave some engineers with unacceptably slow merge request pipelines. This seems to be the case for **stable branch pipelines**, sometimes **taking around 3 hours to complete**. Having an overview of the post-merge deployment pipelines would also help us understand whether the work we are focusing on would improve those pipelines as well, or whether we would need a different approach for them. ## Goal Have a discussion with the ~"group::delivery-release" group to understand their pain points when it comes to **pipeline stability** for **stable branch pipelines** and for **deployment, post-merge pipelines**.