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

Re: 1.7 alpha3 bug (assert/exception) during update

From: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 19 Jul 2011 20:15:59 -0400

On Tue, Jul 19, 2011 at 8:03 PM, Greg Stein <gstein_at_gmail.com> wrote:

> On Tue, Jul 19, 2011 at 19:18, Daniel Shahaf <d.s_at_daniel.shahaf.name>
> wrote:
> >...
> >> BTW: Someone mentioned using svn 1.7 beta1 and some said it was not
> >> released yet. Collabnet disagree as beta1 is listed here:
> >>
> https://ctf.open.collab.net/sf/frs/do/viewRelease/projects.csvn/frs.svn_binaries.windows
> CollabNet should not have posted that tarball. It was never blessed
> and released by the Apache Subversion team. In fact, we *withdrew* our
> beta1 candidate. There is not, and never will be, a 1.7.0 beta 1.
CollabNet did not post anything. In an open-source project (mine), on a
hosting site operated by CollabNet, I posted my Windows binaries in a
listing labelled "Development Builds" just as I have been doing from trunk
for months. This is not different than TortoiseSVN, Subclipse or AnkhSVN
which all post nightly builds so people can try our software. I did not
post the source tarball, I posted my build of the Windows binaries and I
will likely continue to do so as the branch progresses towards release.

I made no special announcement about this, just as I have not for any of the
other updates to the binaries I have made in the last several months. After
building beta1 and running the performance benchmarks I simply posted the
binaries for others to try them. I am not even the one that added a link to
these binaries from the Subversion website.

That said, I do encourage Windows users to download the binaries and
continue to provide us feedback. There are no known show-stopper bugs in
beta1, feel free to use at your own discretion.

Mark Phippard
Received on 2011-07-20 02:16:32 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.