[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Change to Subversion PMC rule for approving backports

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 30 Aug 2019 03:49:04 +0000

Julian Foad wrote on Thu, 29 Aug 2019 15:36 +00:00:
> 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?

What do you propose to do about the rule that changes to tools/ or
bindings/ require 1×+1 and 1×+0? It would be odd if changes to tools/
required more votes than changes to core.

I think that section as it stands (before your change) is pretty hard to
follow: it jumps back and forth between different topics. I might take
a shot at clarifying it (without semantic changes), if that won't
conflict with patches you have in flight.

Cheers,

Daniel
Received on 2019-08-30 05:49:36 CEST

This is an archived mail posted to the Subversion Dev mailing list.