Suhail Singh <suhailsingh...@gmail.com> writes:
> If the goal is to increase the frequency of releases while maintaining
> quality, the only consideration that the teams-branch ought to make is
^^^^^^^^^^^^
> to ensure that the commit in question (corresponding to the release)
> builds correctly (i.e., may, in future, do some automated testing beyond
> the test suites included in the individual packages) past some threshold
> (i.e., on platforms of interest etc.). Importantly, instead of making a
> release soon after a major merge, such a team may decide to not make a
> release too close to major changes.
I meant release-team, above.
--
Suhail
