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

Re: More on possible problem with Neon 0.25.0 [was Re: 1.3.0 RC1 ready to be rolled]

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-10-14 21:41:57 CEST

On Fri, 2005-10-14 at 15:12 -0400, John Peacock wrote:
> The problem is, as I found out, that any ad hoc testing of Neon with
> Subversion was not enough. At least on _my_ machine, 0.25.0 fails when
> compression is enabled and that failure was known to the Neon
> developers, but that information never penetrated into the INSTALL file.
> I'm trying to prevent my issues from coming up in the future, rather
> than just relying on good behavior on the part of our dependencies.

Using the 0.25.0 situation as justification is bogus. It's to be
expected that there may be regressions in x.y.0 releases of software;
regressions are not generally expected in x.y.z releases.

> > Anyway, your attitude is decidedly unfriendly to upstream maintainers.
> > How would we feel if we found out that people weren't upgrading from svn
> > 1.3.0 to svn 1.3.1 because Eclipse was only working with svn 1.3.0 due
> > to a similar policy?
> If there were any serious problems that 1.3.1 fixes, that would act as a
> pressure on the Eclipse team to make a new release. However there are a
> couple of things that your scenario ignores:
> A) Eclipse would still work with 1.3.0 and indeed works without
> Subversion installed at all.
> B) Subversion, on the other hand, cannot use ra_dav with 0.25.0 (at
> least on my machine) in the default configuration.

I don't understand this argument at all, but Eclipse was a random
example pulled out of a hat. If we found out that external projects
were discouraging people from upgrading to Subversion bugfix releases
simply because they hadn't gotten around to testing our bugfix release
themselves, we would be rightly peeved at those projects.

Also, there could be serious problems that 1.3.1 fixes, but no ones that
are interesting to the external project. Just ones that, say, generate
a lot of traffic on our users list.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 14 21:43:32 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.