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

Re: Repo access on tigris.org

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-03-07 17:31:42 CET

Lübbe Onken wrote:
> Leon Zandman wrote:
>
>> Seems to me like that repo has quite some downtime. Maybe you should
>> switch TSVN to SourceForge? They have SVN support now.
>
> And with Steve's commit frequency we would skyrocket to rank #1 in the list
> of most active projects ;-)
>
> Sourceforge offered us to be part of the SVN beta test program, but at that
> time we declined because collab.net seemed to have everything up and
> running.

If we switch to sourceforge with the repo, what would keep us on
tigris.org? We don't use their issue tracker because they refuse to
change the config so that only people with project roles can create new
issues (something even the Subversion guys find *very* annoying). The
FAQ and our docs already are on sourceforge, the downloads too.
The only thing we still use from tigris.org is the mailing list (and
that's a little bit better than the one on sourceforge, which has the
tendency to keep mails for some time and then send them all at once -
I've seen that a lot, it usually keeps them for 15-30 minutes, which
isn't very good for discussing stuff).

Has anyone heard about how reliable the repos on sourceforge are? What's
the downtime? Maybe someone knows the average downtime of the CVS repos
there?

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 Tue Mar 7 17:35:11 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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