[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: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-01-14 19:58:26 CET

On Jan 14, 2005, at 12:39 PM, 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.

kfogel was also saying today that he thinks we should release 'beta'
tarballs of bugfix releases, so that they can be tested for a few days.
  I guess it's a bit silly that we finish merging patches, roll the
tarball, test for an hour, then ship it. We should allow more time for
testing tarballs -- even the bugfix releases.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 14 19:59:34 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.