SteveKing <stefankueng@gmail.com> writes:
> On 7/7/05, Simon Large <simon@skirridsystems.co.uk> wrote:
> > SteveKing wrote:
> > > Also, the repository won't be hosted on a 1.2.x server but on a version
> > > 1.1 server.
> >
> > That means we have to use old the API to get log messages :-(
> >
> > How come Tigris don't want to keep up with the current release?
>
> I haven't asked. I guess they only want *very* stable releases and not
> use the most current one all the time.
Tigris.org is (now) treated like any other CollabNet customer, which
means that software isn't upgraded willy-nilly just because somebody
pops out a new version. CollabNet has historically released software
about twice a year(-ish), and now that Tigris.org isn't just a box
maintained (or more accurately, *not* maintained) by volunteers,
there's no reason to believe that it would be upgraded with each new
CollabNet release (and obviously even more often where security issues
arise). Yes, that means that at any given time, the Subversion
installed on the machine could be six months to a year old, but them's
the breaks, kiddo. You're getting a fully tested CEE instantiation,
administered by folks paid to do so and to do so well, with not just
Subversion, but Subversion integrated with a unified permissioning
system, mailing lists, ViewCVS, Project Tracker, ...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Jul 8 09:59:48 2005