Paul Schweigert

cc @houshengbo One thing to note is that v1.2 went EOL [earlier this month](https://github.com/knative/community/blob/main/mechanics/RELEASE-SCHEDULE.md#historical-no-longer-supported-releases)

/lifecycle frozen

/remove-lifecycle stale

Ran into this one again this morning on #2608 Seems like there's a race happening somewhere. Running the test individually doesn't seem to cause a problem (N~=50): ```console $ go...

Yeah, we went back and forth on the name just a bit :smile: There's a fairly long [slack thread](https://knative.slack.com/archives/C9CV04DNJ/p1658938603476139) where we went over the various iterations.

whoops, missed the whitespace failure... fixed now

> @psschwei is this only for the upcoming latest version or does it need to be cherrypicked to any others? just the upcoming release, no need to cherrypick

I'm ok with the levels proposed. Should we set a target date for meeting those thresholds so that components have time to meet the new standards if they aren't already...

Does by the next release (v1.9 on Jan 24, 2023) sound like a good deadline?

> I didn't understand the "existing _example line" thing, but am wondering if that could be a part of my issue? Maybe that was part of a side conversation. What...