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

Re: you're going to kill me, but... [Re: svn commit: r31625 - branches/1.5.x]

From: Mark Phippard <markphip_at_gmail.com>
Date: Mon, 9 Jun 2008 07:35:54 -0400

On Mon, Jun 9, 2008 at 1:10 AM, Karl Fogel <kfogel_at_red-bean.com> wrote:

>> I have had several fellow committers take indirect swipes at me on IRC
>> or in this list. Saying that I do not understand what a release
>> candidate means etc. It is pretty clear to me though, that if we were
>> not going through this process and "threatening" to release then the
>> software would never get tested. The last few bugs reported make that
>> clear. This bug in particular has been sitting in the code since
>> November 2007. I am assuming this bug impacts SVK, since clkao
>> reported it and I have seen some other talk of segfaults from SVK
>> users. Does this mean that no one has tried SVK with 1.5 code until
>> the last week? If that is true, are we saying they cannot wait until
>> 1.5.1? I've been testing the Java API daily since last summer.
> I think David's last sentence was just a strongly-worded way of saying
> what he thinks our best course of action is, nothing more -- no swipes
> at anyone. (At least, that's how it looked from here!)

I am sorry too. That was just a poorly worded segue to a topic I
wanted to bring up at some point. I did not mean to imply David was
doing that, or even had done that in the past. As I said, I also do
not disagree with the need to backport this. I do disagree with any
notion that we are compelled to fix every bug we find before we can
ship. Clearly that is not the case and there are plenty of bugs more
significant than some of these that we have not even tried to fix.

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-06-09 13:36:10 CEST

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.