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

Re: What's involved with signing/testing releases?

From: Daniel Rall <dlr_at_collab.net>
Date: 2007-01-19 18:24:47 CET

On Thu, 18 Jan 2007, Justin Erenkrantz wrote:

> On 1/18/07, Ed Hillmann <edhillmann@yahoo.com> wrote:
> >I've been lurking on the dev list, and I've noticed how various people are
> >signing and testing releases on various platforms. Is there much involved
> >with this?
>
> No, not really - most folks are just downloading the release,
> compiling it, and trying it out. Each person comes up with their own
> metrics as to how or why they choose to vote for a release. Most
> committers tend to run some combinations of the regression test suites
> to determine whether the release is suitable for public consumption.

Signing is described here:

  http://subversion.tigris.org/hacking.html#tarball-signing

> >I typically build our Subversion on a Solaris 9 environment for our own
> >use internally. If no one is already checking this environment, I'd be
> >happy to help out with this (if someone can nudge me in the right
> >direction). :)
>
> If there's something broken with a release, we want to know about it
> as soon as possible. So, everyone on this list should feel free to
> test the releases in their own environment. The one thing we ask is
> that downstream developers and packagers do not release anything with
> this new code until we have completed our testing and posted it on the
> official Subversion site.
...

Additional testing on Solaris would be fantastic, Ed.

  • application/pgp-signature attachment: stored
Received on Fri Jan 19 18:25:06 2007

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