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

Re: r11557

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2004-10-31 18:24:20 CET

"Peter N. Lundblad" <peter@famlundblad.se> writes:

> In 1.1.x/STATUS philip asks how to check if this works. There is a recipe
> in issue 1905 that could be used. You just have to merge the addition of a
> file with spaces in its name and check the copyfrom URL.
> JUst so you know if you want to vote.

Oh, I know how to do it, I was just being awkward to make a point. If
someone cares enough about a bug to fix it then writing a regression
test ensures that it stays fixed.

In this particular case I assume the person who committed the change
tested it as described in 1905 and that it works. Who is responsible
for testing it on the branch? Is the release manager expected to
merge the STATUS changes, run the regression tests and then look for
manual regression tests as well? Does the release manager have to run
the manual regression tests before the merge to observe the failure,
thus ensuring that they are being done correctly?

Even just staying fixed should not be taken for granted. In the past
some of my libsvn_wc modifications have changed, i.e. "broken", things
that were not regression tested.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 31 18:24:46 2004

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.