Lübbe Onken wrote:
> Go to sourceforge.net/projects/gaim and look how often their beta has been
> downloaded... Maybe not a good example, since that is a feature rich beta.
They have multiple betas, but for a *major* release. Not for an
intermediate release.
> Go to sourceforge.net/projects/firebird. Their win32 RC2 has been downloaded
> 600 times. They have a smaller user base than TortoiseSVN, but still 600 RC
> downloads (for one platform).
Again, RCs for a major release. If you check their intermediate releases
you won't find RCs either.
>>> Sorry, this is just a concatenation of assumptions, made up to
>>> justify that you don't want to create RCs. If you don't want create
>>> RCs, for intermediate releases, don't do it (see below).
>> Sure these are assumptions. The same as your assumption that an RC
>> would have prevented this bug from going into the final release.
>
> Since you were flooded by crashreports, I'm convinced that this particular
> bug would not have made it into the release. More testers = more
> configurations, more use cases. It can only help us.
It all depends on what you think is "flooded" with reports. You haven't
seen _one single_ report on the mailing list about this. What I caught
with the crashreports was about three a day with that crash, usually all
three from the same person (they tried several times and it crashed
every time, and every time they sent the report). And since this was a
bug which was already fixed but got missed when backporting (only one of
two revisions was backported, that's why it crashed), I was annoyed.
>
>>> How about a poll on SF:
>>> Would you test RCs?
>>> ( ) never
>>> ( ) maybe
>>> ( ) of course
>> Also ask if they would actually *report* a bug if they would find one.
>> Some people just try out RC because of the new features, they're not
>> interested in reporting bugs (I do that too with some programs).
>
> See if you like http://tortoisesvn.sourceforge.net/node/206/
Right now, at 17:34 CET there are eight votes. Four of them would
install an RC but not report anything, the other four would *maybe*
report it if they found something serious. So you see, exactly my point.
>> I really don't get why you want an RC for intermediate releases too.
>
> Because it hurts me physically if this kind of bug slips through.
Please explain the physical pain here.
>> Even the Subversion project sometimes has to make a 'fast'
>> bugfix release.
>
> That's no reason not to try to make it better.
There's a line between trying to be perfect and getting things working.
You can always do more to make something even more stable and find even
more bugs which might otherwise have slipped through. But the more you
try, the less work you get done actually improving the product. You
could even go that far that you don't add anything new anymore.
If someone else is willing to do the whole release thing, then ok, let's
do it. But as long as I'm the one who has to do it, I have to say no
here. A release keeps me busy for a whole evening, time which I could
spend otherwise.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Jun 16 17:40:49 2006