On Wed, Feb 9, 2022 at 2:19 PM Stefan Sperling <s...@elego.de> wrote: > > On Wed, Feb 09, 2022 at 08:01:26AM -0500, Mark Phippard wrote: > > Anyway, my feeling has been that one of the blockers to being RM is > > motivation. My feeling has been that it is a fair amount of work that > > might not go anywhere because we do not have enough interest in > > reviewing and signing the release. So why put in the effort to do this > > when the votes are not going to happen? > > It is a bit of a chicken and egg problem. We have never had a problem > getting the release out the door once an RM did step up. Enough people > always joined in to help once the ball got rolling.
Indeed. In recent years we never had a problem getting enough PMC testers and signatures. In fact, getting my build environment dusted off again, and testing and signing releases, is about the only thing I still do around here :-). So, dear RM, just give me a tarball (or release zip I should say for Windows, I guess), and I'll give it a go. > > We have also always had what I > > thought was a peculiar policy that the RM's votes did not "count". So > > often the most motivated member of our community steps forward to do > > the RM work, and now we have lost the one sure thing vote we would > > have had for the release. > > We have already made the RM's vote count during our most recent releases, > as far as I remember. At least I did it that way to expedite the process. > The ASF requires release signatures by at least 3 PMC members. Any further > restrictions are self-imposed and can be avoided if needed. Yes, the last couple of releases we relaxed our old "3 *nix + 3 windows" requirement to just "3 PMC sigs (of which at least 1 *nix and 1 Windows)" [1]. That last part (1 *nix and 1 Windows) is a Subversion-PMC-self-imposed requirement, which could in theory be lifted (depending on consensus of the PMC), but I'm not sure we should. In any case, so far we've never been blocked by this. For me that's also one of the main differences between votes in STATUS and votes on the release. The voting requirements are different (not only the "1 *nix and 1 Windows", which applies only to release votes; but also the rule that backports of bindings and a couple of other things only require 2 votes in STATUS). Also: a vote in STATUS does not necessarily imply that I have run the entire testsuite across 3 ra flavours etc. So a vote there does not mean the same thing as a release vote. [1] https://subversion.apache.org/docs/community-guide/releasing.html#releasing-votes -- Johan
