Author Topic: SourceForge to Release SVN in Feb. 2006  (Read 5291 times)

Offline Game_Ender

  • Lives here!
  • ****
  • Posts: 551
SourceForge to Release SVN in Feb. 2006
« on: January 13, 2006, 06:35:41 pm »
They are currently beta testing Subversion at SourceForge.  They are going to release it to everyone else in Febuary.  The news is here: https://sourceforge.net/docs/A03#january-2006.

Does this mean Code::Blocks will move back to SourceForgre?

Offline Ceniza

  • Developer
  • Lives here!
  • *****
  • Posts: 1441
    • CenizaSOFT
Re: SourceForge to Release SVN in Feb. 2006
« Reply #1 on: January 13, 2006, 06:38:02 pm »
Don't think so. Most ppl has complaint about speed access to SF's repositories and say berliOS is faster for them.

Offline Game_Ender

  • Lives here!
  • ****
  • Posts: 551
Re: SourceForge to Release SVN in Feb. 2006
« Reply #2 on: January 13, 2006, 06:40:39 pm »
The web access on the Berlios through WebSVN/ViewCVS is quite slow though.

Offline Ceniza

  • Developer
  • Lives here!
  • *****
  • Posts: 1441
    • CenizaSOFT
Re: SourceForge to Release SVN in Feb. 2006
« Reply #3 on: January 13, 2006, 06:51:36 pm »
Well, you don't checkout thru WebSVN/ViewCVS :)

I wouldn't mind getting back to SF when SVN be ready, for me it's just the same.

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: SourceForge to Release SVN in Feb. 2006
« Reply #4 on: January 13, 2006, 06:53:13 pm »
It's not slower than web CVS access at Sourceforge. But we aren't interested in that as much as in the checkout/update/commit times via SSH which are about a third of what they used to be at Sourceforge. :D

Besides, Sourceforge has been announcing that they are "preparing to plan to beta test" Subversion support for several years now. Since Subversion is perfectly stable and whole bunch easier to install and manage than cvs, I really wonder what they need to prepare for.

They obviously have a working set of servers with a working authentication system. Subverison uses exactly the same services and technologies as cvs does, so if they have cvs running, they really only need to install one rpm to have svn running, too. For some reason, however, this seems to be really complicated.
I do not doubt that it requires an awful lot of work and many months of planning and development to get a site such as Sourceforge up and running, but that work has already been done a long time ago. The amount of work needed to add Subversion to that working system is quite ridiculous compared to that.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Re: SourceForge to Release SVN in Feb. 2006
« Reply #5 on: January 13, 2006, 06:58:23 pm »
The web access on the Berlios through WebSVN/ViewCVS is quite slow though.

I 'd say it depends. For me, there is no comparison whatsoever on the speeds of the two sites. BerliOS is very fast, at least for us Europeans.
The only time I have to deal with SF anymore is for bugs/patches and I really hate it when I have to. The speed is worse than a 33.6K modem...

SF speeds used to be normal, not really fast, but normal. But somewhere in mid-2005 speed went under...
Be patient!
This bug will be fixed soon...

Offline artoj

  • Almost regular
  • **
  • Posts: 206
  • Location: Supporting my team
    • http://ajonsson.kapsi.fi/
Re: SourceForge to Release SVN in Feb. 2006
« Reply #6 on: January 13, 2006, 07:09:15 pm »
The only time I have to deal with SF anymore is for bugs/patches and I really hate it when I have to. The speed is worse than a 33.6K modem...

Why the bug and patch trackers are on SF.net (and not in Berlios)?

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: SourceForge to Release SVN in Feb. 2006
« Reply #7 on: January 13, 2006, 07:16:35 pm »
If you know a way of migrating them, please tell. They'll be gone tomorrow :)
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Re: SourceForge to Release SVN in Feb. 2006
« Reply #8 on: January 13, 2006, 07:17:30 pm »
The only time I have to deal with SF anymore is for bugs/patches and I really hate it when I have to. The speed is worse than a 33.6K modem...

Why the bug and patch trackers are on SF.net (and not in Berlios)?

Because we can't find a reliable way to transfer the existing tracker data. If someone knows about the process, please step forward :)
Be patient!
This bug will be fixed soon...

Offline artoj

  • Almost regular
  • **
  • Posts: 206
  • Location: Supporting my team
    • http://ajonsson.kapsi.fi/
Re: SourceForge to Release SVN in Feb. 2006
« Reply #9 on: January 13, 2006, 07:21:09 pm »
Because we can't find a reliable way to transfer the existing tracker data. If someone knows about the process, please step forward :)

But could you slowly migrate to Berlios e.g. all new bugs/patches should be filed there?

Offline yop

  • Regular
  • ***
  • Posts: 387
Re: SourceForge to Release SVN in Feb. 2006
« Reply #10 on: January 14, 2006, 12:00:12 am »
Because we can't find a reliable way to transfer the existing tracker data. If someone knows about the process, please step forward :)

But could you slowly migrate to Berlios e.g. all new bugs/patches should be filed there?
Generally it's not a good practice to split your bug reports. Consider them to have the same significance as the source repository, you wouldn't want to lose the older revisions of your code would you? The same applies for the reports.
Life would be so much easier if we could just look at the source code.

Offline takeshi miya

  • Lives here!
  • ****
  • Posts: 1487
Re: SourceForge to Release SVN in Feb. 2006
« Reply #11 on: January 14, 2006, 12:27:16 am »

I've found this bash script to webcrawl the bugs of sourceforge: http://casper.ghostscript.com/~raph/crawl-sf-bugs
If anyonecan write a script to adapt it to a new bug tracking system (either berlios tracker, or bugzilla, or trak, etc) would be great.

Seems that sf may have an XML export option, too: http://sourceforge.net/docman/display_doc.php?docid=24202&group_id=1#xml_export

Additional links:
http://www.advogato.org/article/357.html
http://mail.wikipedia.org/pipermail/wikitech-l/2004-August/024517.html