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

Re: change release signature requirements?

From: Julian Foad <julianfoad_at_apache.org>
Date: Fri, 29 Jun 2018 16:38:52 +0100

Stefan wrote:
> new:
> [...] 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[1] 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.
Do you want to go ahead and update it (after waiting 5 days for anybody
else to chime in)?
- Julian

Links:

  1. https://people.apache.org/keys/group/subversion-pmc.asc
Received on 2018-06-29 17:39:04 CEST

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