Re: Where shall we go?

[steps out of the dark]

On Mon, Mar 16, 2015 at 9:11 AM, Lübbe Onken <luebbe.tortoisesvn_at_gmail.com>
wrote:

> Hi folks,
>
> it would be a kind of heresy to move a SVN client repository to Github or
> Bitbucket, wouldn't it? ;)
>

If I had to chose, these would be my criteria

1. Lossless repo migration (including mergeinfo etc.)
2. More or less complete SVN feature set (dogfooding)
3. Reliable service (availability, account and other management overhead)
4. Bonus: One of our currently used sites (tsvn.net, SF)
5. Bonus: Issue tracker migration.

1 and 2 exclude GitHub and Bitbucket.
3 limits the options to hosting companies, i.e. excludes the offers from
WANdisco and VisualSVN.

That leaves us with SF and Assembla. 4 and 5 favour SF.

> I don't have a real preference or a good suggestion. For me sourceforge
> would be ok. We already host our downloads there and we wouldn't need yet
> another login for yet another hoster.
>

TSVN's project history shows that there will be a migration
every 5 years or so. SF seems like a reasonable bet for
that time frame.

Another option could be to move the issue tracker to some
Trac installation on tsvn.net. This might make sense if the
issue tracker on SF is cumbersome to use or integrate with
TSVN props or if the issues can't be migrated directly from
Google Code to SF. But having it on tsvn.net may require
extra account management.

-- Stefan^2.

[back into the dark]

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3105563

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-03-19 18:37:57 CET