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

Re: Release, bindings (Was: svn commit: r12731 - trunk/notes)

From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2005-01-15 21:08:31 CET

On Fri, 14 Jan 2005, Jani Averbach wrote:

> On 2005-01-14 12:12-0600, sussman@tigris.org wrote:
> >
> > Document that our release process should at least *compile* bindings.
> >
> > No, it's not the same as real testing, but at least it avoids any
> > brown-paper-bag releases like svn 1.1.2. It's one thing to ship a
> > tarball with bugs; it's a whole separate level of embarrassment to
> > ship a tarball that doesn't fully compile.
> I would like to see that our release process mandate that we won't cut
> tarball from branch until 24-48h hours after the last merge.
> This way someone else has a fighting chance to test branch, and our
> smoke testers has time to kick in.
> At the moment, svntester runs unit tests for swig-pl and javahl, and
> verify that swig-py compiles and installs.

Yes, please, give a few days before "official" releases.

Several times, releases have been put out and I've been busy enough that
I've not had time to try to build the RPMs, only to find out later that
they fail compiling. (1.1.2 was the latest example).

Also I would like to point out that my RPM build for RedHat 7.3, 8.0, 9.0,
FC1, and WBEL3/RHEL3 exercise the compile, the perl and python bindings
compiles and any tests they have, and all the unit tests for Subversion
for ra_local, ra_dav, and ra_svn. While not "perfect", just building the
RPMs exercises a lot of subversion and dependent package compiles, tests,
and functionaltiy. Of course that is only for these platforms and not
others, but for devs with those platforms it is a pretty good test.

When these problems happen then I have to release a "special" build that
includes the path and %changelog entries to detail exactly how the RPM was

Normally, when everything works right, I just check out the tag and go to
the appropriate packages/rpm/<distro> directory and do "make RELEASE=1"
and wait a couple of hours (the tests take a long time but are worth it.)

David Wayne Summers          "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  0B44 B118 85CC F4EC 7021  1ED4 1516 5B78 E320 2001
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 15 21:09:44 2005

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.