Unless anyone objects, I'd like to bite the bullet and just haul everything over into SVN. SVN is not _that_ different from CVS, so I don't forsee a huge adjustment period.
- get everyone with stuff pending in their CVS working copies to get themselves to a good stopping point and commit
- turn on SVN
- freeze CVS
- wait a day or two for everything to settle
- migrate repo to SVN
- continue development in SVN; leave CVS frozen
-mental
On Jan 14, 2006, at 6:36 PM, MenTaLguY wrote:
Unless anyone objects, I'd like to bite the bullet and just haul everything over into SVN. SVN is not _that_ different from CVS, so I don't forsee a huge adjustment period.
Anyone know of a good GUI tool comparable to TkCVS feature-wise?
That was one thing that wasn't there originally, but might have come up since then.
Jon A. Cruz wrote:
On Jan 14, 2006, at 6:36 PM, MenTaLguY wrote:
Unless anyone objects, I'd like to bite the bullet and just haul everything over into SVN. SVN is not _that_ different from CVS, so I don't forsee a huge adjustment period.
Anyone know of a good GUI tool comparable to TkCVS feature-wise?
That was one thing that wasn't there originally, but might have come up since then.
We used JSVN on a previous project once. It did pretty well: http://www.alternatecomputing.com/jsvn/index.php3
Although, SmartSVN might be a good alternative: http://tmate.org/svn/
For those who don't like Sun Java, I would not be surprised if these also ran well on GCJ. Gnu Classpath claims to be quickly approaching full compatibility. Someone might try yum or apt-get to test this.
Of course, on Windows, TortoiseSVN is awesome: http://tortoisesvn.tigris.org/ Would be awesome if there were a Linux analog of Tortoise, integrating SVN into Nautilus.
People might want to start looking here at the Subversion HQ: http://www.tigris.org/
RapidSVN shows promise, but it doesn't seem to be very active these days.
bob
On Jan 14, 2006, at 8:21 PM, Bob Jamison wrote:
Of course, on Windows, TortoiseSVN is awesome: http://tortoisesvn.tigris.org/
Well, it's good for some things. But for others it is not as good as different tools.
To give you an idea, when working with CVS hosted things on a Windows box, I install TortoiseCVS and TkCVS both. (WinCVS is much of what makes Windows people hate CVS, IMHO)
Would be awesome if there were a Linux analog of Tortoise, integrating SVN into Nautilus.
I could probably do it... but for me that's not my workflow.
(Adding a menu to things can be done via scripting if you don't want to use CORBA or a later GNOME)
On Sat, 2006-01-14 at 19:34 -0800, Jon A. Cruz wrote:
On Jan 14, 2006, at 6:36 PM, MenTaLguY wrote:
Unless anyone objects, I'd like to bite the bullet and just haul everything over into SVN. SVN is not _that_ different from CVS, so I don't forsee a huge adjustment period.
Anyone know of a good GUI tool comparable to TkCVS feature-wise?
Another that hasn't been mentioned is eSvn: http://esvn.umputun.com/ which is written in QT. I much prefer it over RapidSVN personally, although it isn't without its faults.
Jon A. Cruz wrote:
On Jan 14, 2006, at 6:36 PM, MenTaLguY wrote:
Unless anyone objects, I'd like to bite the bullet and just haul everything over into SVN. SVN is not _that_ different from CVS, so I don't forsee a huge adjustment period.
Anyone know of a good GUI tool comparable to TkCVS feature-wise?
That was one thing that wasn't there originally, but might have come up since then.
How about TkCVS (also now known as TkSVN)? I'm not a big TkCVS user, but see the large notice of subversion support at http://www.twobarleycorns.net/tkcvs.html
By and large, SVN GUI options are as available and varied as CVS these days.
John
On Jan 15, 2006, at 9:16 AM, John Pybus wrote:
How about TkCVS (also now known as TkSVN)? I'm not a big TkCVS user, but see the large notice of subversion support at http:// www.twobarleycorns.net/tkcvs.html
YAY!!!!!!
I'd been checking it periodically, but they'd just kept their FAQ entry that they wouldn't be supporting SVN.
I'm not sure when they changed, but I had been by there in just the past few months. Now I just have to wait for Fink to catch up. :-D
By and large, SVN GUI options are as available and varied as CVS these days.
Good. Because even only a year ago they were missing some strong workflow tools for certain people.
On Sat, 14 Jan 2006, MenTaLguY wrote:
Date: Sat, 14 Jan 2006 21:36:39 -0500 From: MenTaLguY <mental@...3...> To: Inkscape ML inkscape-devel@lists.sourceforge.net Subject: [Inkscape-devel] SVN migration
Unless anyone objects, I'd like to bite the bullet and just haul everything over into SVN. SVN is not _that_ different from CVS, so I don't forsee a huge adjustment period.
get everyone with stuff pending in their CVS working copies to get themselves to a good stopping point and commit
turn on SVN
freeze CVS
I get the impression when you say frozen you mean completely frozen, and no longer updated whatsoever.
wait a day or two for everything to settle
migrate repo to SVN
continue development in SVN; leave CVS frozen
Would it be too much trouble to continue offer basic read access against CVS? Keep it simple for those struggling to provide an occossional patch?
- Alan
On Sun, 2006-01-15 at 13:30 +0000, Alan Horkan wrote:
I get the impression when you say frozen you mean completely frozen, and no longer updated whatsoever.
Yes.
wait a day or two for everything to settle
migrate repo to SVN
continue development in SVN; leave CVS frozen
Would it be too much trouble to continue offer basic read access against CVS? Keep it simple for those struggling to provide an occossional patch?
Well, we would need software to collect SVN commits and automatically back-apply them to CVS, ideally with the commit metadata as intact as is reasonably possible.
I don't think that's going to happen unless someone volunteers to write it. I'm not sure it's worth the effort, either -- SVN isn't hard to learn, and I'd say it's easier than CVS for casual users to work with.
-mental
participants (6)
-
Alan Horkan -
Bob Jamison -
John Pybus -
Jon A. Cruz -
Jonathan Leighton -
MenTaLguY