Move repository to subversion?

[mandrav]

Last week, SF CVS was misbehaving badly resulting in the corruption of two newly added files last Friday. I had to rewrite them almost from scratch. I don't need to tell you that I was really pissed off  :x.
They supposedly "plan" support for subversion for at least a year now. Every now and then, they release a mail that svn support is planned, etc, etc. Leave alone the fact that I don't really understand what's to plan: setup a machine like you would for cvs, install subversion, done.

I 'm tired of waiting, really. So, there's a thought to move the repository to berlios.
So, what does the community think?

[therion]

IMHO, its the best versioning system among the free ones (Clearcase/Clearquest rox).
Great features to work offline ;-)

[takeshimiya]

I know for sure the answer of thomas :lol:

I don't have problems if you're going to move *only* the repository to BerliOS SVN, but not the entire site.

SVN support in sf.net is in testing stage, they're redesigning all the whole SourceForge (did you noticed that they changed the CMS SF uses for the site in the last week?)
but they haven't said an ETA yet. See the sf.net blog here: http://blog.dev.sf.net/

You could move the repository to BerliOS in the mean time, and when SF haves support ready for SVN then move the repository back (this is what they recommend also).

[thomas]

You could move the repository to BerliOS in the mean time, and when SF haves support ready for SVN then move the repository back (this is what they recommend also).

Lol? They can't be serious.

[takeshimiya]

Haha, yep, they doesn't say explicitly say BerliOS.

Quoted from sf.net:
We also ask that you not install or configure Subversion to use
the project shell server for your repository. The purpose of
that
system is simply to allow you to maintain your project web
site,
not for actual development (the load is already high enough).
Please find another host for Subversion usage.

Thank you,

SourceForge.net Support

[takeshimiya]

UPDATE: As a developer you can submit your project to be in the list of beta testing of SourceForge SVN.

For that you must fill a Feature Request like this.

[mandrav]

I don't have problems if you're going to move *only* the repository to BerliOS SVN, but not the entire site.

Yes, I 'm talking about the repository. The site isn't on sourceforge anyway...

SVN support in sf.net is in testing stage

Our progress on CVS performance and reliability has freed up resources
to begin planning deployment of a long-awaited Subversion offering.

They want to "begin planning" subversion support... They 're in this "begin planning" stage for over a year...

As a developer you can submit your project to be in the list of beta testing of SourceForge SVN.

I have, but I don't hold my breath

[kisoft]

...
They want to "begin planning" subversion support... They 're in this "begin planning" stage for over a year...
...

Bad

My hot head said SVN!
My cold mind said CVS.

I vote to SVN, I love it more.

[Der Meister]

I also would prefer SVN on Berlios - not only because it's SVN but Berlios seems to have much less performance problems than sf.net...

[MortenMacFly]

I would generally agree. Recently I had the same thoughts at work where I (with a small group of other developers) use CVS. Subversion is really promising and already stable. Also converting CVS to Subversion worked from scratch with the tools provided by tigris.org (at least for me).

But: In the end we did not switch because of the lack of GUI's for Subversion. A lot are being developed but besides Tortoise in my opinion none is ready-to-use. For us, Tortoise was no option because of the Explorer integration - we clearly prefer a stand-alone program. I don't know, if this is important for Code::Blocks, I just thought it might be helpful to share that experience.

Morten.

[thomas]

Well, there is RapidSVN if you absolutely must have a standalone program.
And of course, you could always call TortoiseProc directly

[MortenMacFly]

Thanks for the hints!

Well, there is RapidSVN if you absolutely must have a standalone program.

I know about that, I just checked the webpage and: It has indeed changed a lot (the last version I gave a try was 0.60 which crashed far too often...). The only thing I am not sure of: The webpage states that one is required to use SubVersion v1.00 which is really old and has quite a few bugs. But maybe it will also work with a recent version...?! I should give it a try...

And of course, you could always call TortoiseProc directly

Yes, that's right, but I LOVE GUI's (I have used MS-DOS too long). I don't like playing too much with command-line tools. Why do you think I am using Code::Blocks...?! :lol: :lol: :lol:

Morten.

EDIT: Uuuh! This was my 100'th post, now I "live here." :shock:

[thomas]

Subversion up to and including 1.2.3 is  downwards compatible to Subversion 1.0.
TortoiseProc is the GUI part of TortoiseSVN.

[anonuser]

Anyone suggested perforce? They are really powerful and will give you their software provided you're opensource.
I'll be happy to setup the server and such.

[thomas]

--->Money?