Re: change release signature requirements?
On 29/06/2018 17:38, Julian Foad wrote:
> Stefan wrote:
>> [...] Before a release is officially made public, it must receive
>> three +1 votes from members of the Subversion PMC. In addition, as a
>> matter of project policy, we require testing and signatures from at
>> least one PMC members on /each/ of the major platforms we support:
>> Windows and *nix. [...] (A list of the current public keys
>> <https://people.apache.org/keys/group/subversion-pmc.asc> for members
>> of the Subversion PMC is autogenerated from LDAP each day.)
> Looks Good To Me.
> That will set a compromise between burden and stability that should be
> more suitable for the new regular releases, in particular, and perhaps
> for the LTS releases too. We'll most probably think again about this
> matter when we next do an LTS release so there is no need to think too
> hard about that just now.
>> The release manager is encouraged to wait at least 5 days for the
>> signatures before rolling the release to allow anybody (planning to)
>> test(ing) the release to complete signing the release before it's
>> being rolled.
> Yes, we can add that too. (You're sure it's not there already? It
> sounds very familiar.) Anyway, I agree with the sentiment, and it's
> useful to have such expectations written down.
I thought I'd read something like that at some point too, but skimming
through the community-guide, I couldn't spot such statement and thought
it might have been just my memory about the discussion we had during
last year's Hackathon.
> Do you want to go ahead and update it (after waiting 5 days for
> anybody else to chime in)?
Will do Thursday 2018-07-05 to give everybody enough time to speak up.
If there are no objections by then, will commit the changes directly to
publish (don't see much need to go through staging for this since it's
just rephrasing part of a paragraph).
> - Julian
Received on 2018-07-03 00:54:39 CEST
This is an archived mail posted to the Subversion Dev