I agree... Besides, it is trivially easy to remove a commit if need be. (BTW: Somewhat off topic, I've been working on the test suites and trying to (1) get trunk and 2.4.x in sync, asap, so that there is basically one version that works as expected on both branches and (2) better aligns the 2 distinct implementations. Moving to 1 format is more work than I have the energy for :-) ).
> On Oct 28, 2026, at 7:29 AM, Eric Covener <[email protected]> wrote: > > I don't have very strong feelings about it but I'd like to discuss the > 3 review requirement for RTC branches. > > We are not enforcing anything at the PR level yet, largely because it > would be tricky to handle CTR parts of the 2.4.x tree. > > To level-set, when we say 3 reviews, a typical fix is proposed by the > author and their own vote counts. So in the typical case, it's what > most people would describe as 2 reviews. > > With agents, better testing, CI, and slim participation should we > consider dropping it to 2 reviews total, meaning just 1 separate +1 > for typical cases? Perhaps with a _suggestion_ of getting a third for > more significant changes? > > It is my preference to reduce it and give it a try. If there is some > support here I will spin off a separate [VOTE]. > > -- > Eric Covener > [email protected] -- Jim "This is an outrage!" Tony Harrison
