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

Re: Version of Subversion on svn.collab.net

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-10-10 16:34:08 CEST

Garrett Rooney <rooneg@electricjellyfish.net> writes:

> So I've been wondering... Why are we sticking to released versions of
> Subversion on svn.collab.net?

From svn.collab.net:

   o Subversion: 1.1.0rc2 (plus a tweaked mailer.py)

> So I'd like to propose a policy of testing RCs on svn.collab.net
> before rolling out an actual release

I'm fine with that.

> and beyond that, I think it might be worthwhile to upgrade to dev
> snapshots of trunk from time to time in order to shake out problems
> before they become too intrenched.

No, sir. The Subversion running on that machine should match a
tarball that is publicly available (meaning, either rcX or final

svn.collab.net is *not* a test machine or a staging environment. It
is a critical piece of the development framework for the many folks
that contribute to Subversion, and a primary delivery outlet for the
many more folks that want to simply track HEAD (but aren't
developers). All of these folks deserve to be connecting to software
that we believe to be stable -- stable enough for us to roll it into
tarball, post it, and tell folks they should use it on their own
servers. If a problem is found in one of our release candidates or
final releases that is so bad that we would be tempted to upgrade
svn.collab.net, then that problem is bad enough to require us to roll
a new release candidate or bugfix release, at which time our server
can be upgraded accordingly.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 10 16:36:17 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.