Why just one +1? I like the second eye rule we currently have, so one +1 from the nominator and one additional eye.
For bindings we have +- the same rule, but one of the eyes can be someone else than a full committer. (Not sure if we still have any active partial committers though) As always, feel free to ping me if you need an additional review for something. I don't follow the dev@ list on a daily basis any more :( +1 on reducing the number of required votes to just 2 +1s. Bert On Thu, Aug 29, 2019 at 5:36 PM Julian Foad <julianf...@apache.org> wrote: > To all devs: > > Proposal for a permanent change to our backport rules [1]: > > * For non-LTS releases, each backport nomination only requires one +1 > vote (instead of three). > > Specific diff to the text of [1]: > > - A change needs three +1 votes from full committers (or partial > committers for the involved areas), and no vetoes, to go into A.B.x. > + A change needs three +1 votes (for an LTS release line) or one +1 vote > (for a non-LTS release line) from full committers (or partial committers > for the involved areas), and no vetoes, to go into A.B.x. > > - (If a change affects the build system, however, it is considered a > core change, and needs three +1's.) > + (If a change affects the build system, however, it is considered a > core change, and so for an LTS release line needs three +1's.) > > Agreements? > > > [1] > > http://subversion.apache.org/docs/community-guide/releasing.html#release-stabilization > > - Julian > > > > Branko Čibej wrote: > > On 18.07.2019 14:09, Julian Foad wrote: > >> Recently there have not been enough developers willing and able to > >> test and approve proposed fixes for back-port to the supported release > >> branches. > >> > >> We have just been discussing this on #svn-dev [1]. Rather than delay > >> forever, myself, stsp and brane decided that in line with "silence > >> implies consent", we can go ahead with merging the proposed backports > >> even if they have fewer than 3 votes. > >> > >> We will go ahead now. > > > > Thanks for the heads-up, Julian, and for pushing the releases. [...] >