Everybody,
On Apr 29, 2006, at 11:44 AM, Markus Barchfeld wrote:
Christopher Williams wrote:
Next up is an idea to stew on. We've got a group of german
students who are working on preliminary refactoring support. We've
got RadRails building on top of us. We may have a google summer of
code student as well. Considering those new sources building on
top of what we do - and considering the CVS issues - should we
seriously consider migrating to using Subversion?
What are your gut reactions? I think it would benefit us in terms
of letting others just use externals to keep in synch with us. for
active development. Plus we'd gain the seemingly more stable setup
at SF.net and well - Subversion is supposed to be a better
replacement for CVS already.
My experiences with subversions are not really good ones. I always
struggle with lock problems I can't explain. Nevertheless we could
give it try. Before we switch over we must make sure that the
little functionality we need (check out, commit, versioning,
branches) will be supported from subclipse in a stable manner. I
don't want to have to use the command line client and poor
synchronisation support! Tweaking the nightly build for subversion
is also an issue which needs some adaptation of the build scripts
but should be possible.
My experience with Subversion has been very good. Subclipse is
another story, and has had occasional problems for me (usually
relating to setting properties on a folder or trying to commit a
brand new folder structure - I will sometimes need to do the folder
then its contents). TortoiseSVN is great (for windows).
The question where we should host it also depends on how much
advantages an integration with trac offers. Does anybody know what
these are apart from the "Browse Source" button? (which we also
have with view-cvs).
You also get integration in terms of the tickets. First, you get the
timeline view which will show not only wiki edits and ticket changes,
but also will show checkins (changesets). If you reference a ticket
in your check in comments it will make the hyperlink between the
changeset and the ticket (but won't auto-close it or anything).
Rails' Trac site is a good example of this (or radrails for that
matter). But I think Trac requires the subversion repository to be
housed on the same physical box.
if we really do want to consider a whole new host/box we should go
"whole-hog". Put Cruisecontrol, Trac, Subversion and the update site
on it. Then we'd have one single place for everything and get the
Trac/Subversion integration. Obviously this would mean moving out of
Sourceforge pretty much entirely and we'd need to come up with a
reliable host (and possibly pay hosting fees). I have a lifetime
Textdrive account as well we could use, but I'd be very wary of it -
we'd likely eat up all the bandwidth really quickly when we cut a
release (and get booted from Textdrive or charged big bucks).
Thanks,
Chris
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Rubyeclipse-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
