RubyForge scheduled downtime

[Tom Copeland]

RubyForge will be down from 1300-1530 UTC Monday October 25 for hardware
upgrades. Apologies for the inconvenience!

Yours,

The RubyForge team

P.S. More hardware info and general rambling is here:

http://rubyforge.org/docman/view.php/5/11/rubyforge_site_status.html

 

[Tom Copeland]

RubyForge will be down from 1300-1530 UTC Monday October 25 for hardware
upgrades. Apologies for the inconvenience!

Hi -

RubyForge is up and running on its new hardware - dual 2.8 Xeon CPUs, 2
GB of RAM, 200 GB of SCSI RAID 5 storage with a hot spare:

http://rubyforge.org/

All appears to be well, but if you notice anything awry, please let me
know at (e-mail address removed).

Thanks,

Tom

 

[Tom Copeland]

Hi -

RubyForge is up and running on its new hardware - dual 2.8 Xeon CPUs, 2
GB of RAM, 200 GB of SCSI RAID 5 storage with a hot spare:

http://rubyforge.org/

All appears to be well, but if you notice anything awry, please let me
know at (e-mail address removed).

Also, as part of the upgrade, we bumped the StatCVS version from 1.3 to
2.2. Lots more graphs and charts, i.e.:

http://aeditor.rubyforge.org/statcvs/

Yours,

Tom

 

[Jamis Buck]

Also, as part of the upgrade, we bumped the StatCVS version from 1.3 to
2.2. Lots more graphs and charts, i.e.:

http://aeditor.rubyforge.org/statcvs/

Yours,

Tom

Tom,

http://copland.rubyforge.org/statcvs
http://needle.rubyforge.org/statcvs
http://sqlite-ruby.rubyforge.org/statcvs

Appear to still be using 0.1.3... not that I'm dying for the new
features or anything, but if it was supposed to be an across-the-board
upgrade, I thought you'd like to know that something got missed.

Thanks!

- Jamis

 

[Tom Copeland]

Tom,

http://copland.rubyforge.org/statcvs
http://needle.rubyforge.org/statcvs
http://sqlite-ruby.rubyforge.org/statcvs

Appear to still be using 0.1.3... not that I'm dying for the new
features or anything, but if it was supposed to be an across-the-board
upgrade, I thought you'd like to know that something got missed.

Yup, sorry, I just ran aeditor manually - the rest will be updated when
the cron job runs tonight at 12:30 AM...

Yours,

Tom