[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: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Mon, 25 Jun 2018 10:56:21 +0000

Julian Foad wrote on Mon, 25 Jun 2018 11:33 +0100:
> Johan Corveleyn wrote on 2018-06-25:
> > On Sun, Jun 24, 2018 at 8:20 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> > > While we're on the subject of changing the supported release
> > > process, we could use this opportunity to lower the number of
> > > signatures required for a release.
> > >
> > > While we never failed to meet the current requirements eventually,
> > > our release process could be faster if less signatures were required.
> > >
> > > My suggestion would be:
> > >
> > > ASF guidelines require a minimum of signatures from 3 different people
> > > in total (including the release manager). To this, we could add our
> > > requirement of cross-platform signatures, where at least one signature
> > > must count for a Windows system, and at least one must count for a
> > > Unix-like system. Of course, more than 3 signatures are always welcome.
> > >
> > > We could also reserve an option for the RM to decide to publish a
> > > release with 3 signatures for any platforms, based on the RM's
> > > judgement of the situation (e.g. if a patch release only contained
> > > code changes inside #ifdef WIN32, Unix signatures could be skipped).
> > >
> > > I believe this change would help us with meeting the new 6 months schedule.
>
> +1. This issue has come up in several recent releases.

For clarity, I assume this applies to all future releases, including any
future patch releases of the 1.8/1.9/1.10 lines.
Received on 2018-06-25 12:56:29 CEST

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