Figure out how we identify new critical issues & regressions (across all dev projects) with the switch to gitlab
Over the past 6 months the product maintenance team (core + various volunteers) have gotten the number of critical issues from 13 down to zero. With the switch to gitlabs we should aim to keep the number of criticals at zero. The challenge here is how to identify & triage them. In JIRA we were working off this list: