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

Re: svn commit: rev 6318 - trunk/subversion/libsvn_delta

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-06-23 01:20:53 CEST

cmpilato@collab.net writes:

> To run the test suite over ra_local, ra_dav, and ra_svn is, I'm sorry
> to say, just plain prohibitive to forward motion (generally
> speaking). I mean, we're talking about a four-hour process for some
> folks. So yeah, I admit that I don't run the tests over all three RA
> layers with every commit.
> My policy is just to try to use some common sense when deciding what
> to test. For example, a change to mod_dav_svn doesn't need any
> testing except over ra_dav -- no other RA layers should be touching
> that code.

And we have other QA methods as well.

 1. If anyone ever introduces a compile error into HEAD, we tar and
     feather them. :-)

 2. We use common sense, as cmpilato is describing above. We run
     hand tests, and as many of the python regression tests as seems
     reasonable, before committing. So 98% of the time, HEAD passes
     the regression tests.

 3. People on this list (well, mostly Branko) have nightly-build
     machines on different OSes. They build and test HEAD each night
     on all RA layers, and email the results to
     svn-breakage@subversion.tigris.org. (Go ahead and subscribe!)
     If something breaks in HEAD, we usually see it within 24 hours.

 4. When a release is made, the release maintainer runs the
     regression suite over all RA layers as well.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 23 01:22:41 2003

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.