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

Re: Only require 2 signatures for zip file?

From: Mark Phippard <markphip_at_gmail.com>
Date: Sun, 13 Apr 2008 15:50:55 -0400

On Sun, Apr 13, 2008 at 1:17 PM, Karl Fogel <kfogel_at_red-bean.com> wrote:
> "Mark Phippard" <markphip_at_gmail.com> writes:
> > I used to build the Windows release so I could include JavaHL library
> > in Subclipse, and so I would also run the tests and sign the release.
> > But since I was not a full committer, my signature did not count
> > towards the release. I always thought it should have (since we had
> > these same signature problems back then).
> >
> > Given that the rest of you are not likely to give up emacs for Windows
> > we need to be looking for solutions. By the way, I forgot Ivan Zhakov
> > in my original post. I do not think he has signed releases in the
> > past, at least not regularly. If we could get him to commit to do so,
> > this would at least be less of a problem since we would then have
> > three committers that we can count on signing the release, and four
> > when DJ is able to devote the time again.
> >
> > That said, Stefan, Bert and Jeremy have all contributed to our project
> > and they have vested interest in our releases. It seems like we would
> > be doing ourselves a favor if we recruited and counted their
> > signatures.
> It does seem silly that we pretend these two things are the same
> function:
> 1) J. Random tends to make non-damaging code contributions, and works
> well with people in the community, so we want his changes going
> directly into future releases without them needing prior review
> (in other words: J. Random is a full committer).
> 2) J. Random has built and tested on platform X, and we trust his
> reports of what he encountered (in other words: J. Random can
> sign releases).
> Right now, we pretend that (1) is both necessary and sufficient for
> (2). It is surely sufficient, but it is *not* necessary.
> But is there any qualification we should require for (2), beyond that
> someone posts plausible-looking test output to the dev@ list? Should we
> "know" the person somehow?

If we really wanted to do something, I would suggest adding a "release
signers" section to our COMMITTERS file. We could then nominate
people we trust that are not already committers, such as Stefan King
and some of the AnkhSVN developers etc.

This might also be a way to bring in some of the people that build
stuff off our bindings.

Of course it all presumes that these people want to go through the
process of testing and signing a release.

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-13 21:51:13 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.