Summarizing this thread so far:
In favor of making stress-new non-required:
Kirk
Mark
Myself
In favor of making all PR checks non-required:
Jake
In favor of hashing out a more nuanced balance between making it possible (but
not too easy) to ignore stress-new failures:
Donal
Dale
Maybe that's rough concensus in terms of which option to recommend, but hardly
a thread I would feel comfortable citing as evidence that the community is on
board with striking down a longstanding protection that was enacted through a
[VOTE].
On 6/9/21, 2:11 PM, "Anthony Baker" <bak...@vmware.com> wrote:
If we have consensus, no need to VOTE.
> On Jun 9, 2021, at 12:52 PM, Owen Nichols <onich...@vmware.com> wrote:
>
> Ok, I'm on board with changing stress-new-test from a required PR check
to non-required. It's simple, codeowners still have the final say, and it
neatly avoids the whole topic of overrides. Time to take a [VOTE]?
>
