Spencer and David, My experience of R-Forge :
i) SVN access and project management web pages have been *very* reliable all this year ... up until the weekend. This week was the first time I ever saw "R-Forge Could Not Connect to Database". ii) The nightly build and checks have been consistently unreliable all year. At best the nightly build is a few days behind the latest commit, but they are working on it. This isn't as critical as (i) though since users can install from source: install.packages("<pkg>",type="source",repos="http://R-Forge.R-project.org"). iii) Mailing lists have been down since the weekend and I too have been mailing r-fo...@r-project.org with no response. That is *very* unusual; first time. Hope that helps to put it into context at least. Matthew P.S. I notice that R-Forge appears to be back up now, including the mailing lists. "Spencer Graves" <spencer.gra...@structuremonitoring.com> wrote in message news:4c762b50.7000...@structuremonitoring.com... Hello: Can anyone comment on plans for R-Forge? Please see thread below. Ramsay, Hooker and I would like to release a new version of "fda" to CRAN. We committed changes for it last Friday. I'd like to see reports of their "daily checks", then submit to CRAN from R-Forge. Unfortunately, it seems to be down now, saying "R-Forge Could Not Connect to Database:". I just tried, 'install.packages("fda", repos="http://R-Forge.R-project.org")', and got the previous version, which indicates that my changes from last Friday have not been built yet. Also, a few days ago, I got an error from 'install.packages("pfda", repos="http://R-Forge.R-project.org")' (a different package, 'pfda' NOT 'fda'). I don't remember the error message, but this same command worked for me just now. I infer from this that I should consider submitting the latest version of 'fda' to CRAN manually, not waiting for the R-Forge [formerly] "daily" builds and checks. R-Forge is an incredibly valuable resource. It would be even more valuable if it were more reliable. I very much appreciate the work of the volunteers who maintain it; I am unfortunately not in a position to volunteer to do more for the R-Project generally and R-Forge in particular than I already do. Thanks, Spencer Graves On 8/26/2010 1:07 AM, Jari Oksanen wrote: > David Kane<dave<at> kanecap.com> writes: > >> How reliable is R-Forge? http://r-forge.r-project.org/ >> >> It is down now (for me). Reporting "R-Forge Could Not Connect to >> Database: " >> >> I have just started to use it for a project. It has been down for >> several hours (at least) on different occasions over the last couple >> of days. Is that common? Will it be more stable soon? >> >> Apologies if this is not an appropriate question for R-help. >> > Dave, > > This is rather a subject for R-devel. Ignoring this inappropriateness: > yes, > indeed, R-Forge has been flaky lately. The database was disconnected for > the > whole weekend, came back on Monday, and is gone again. It seems that > mailing > lists and email alerts of commits were not working even when the basic > R-Forge > was up. > > I have sent two messages to r-fo...@r-project.org on these problems. I > haven't > got no response, but soon after the first message the Forge woke up, and > soon > after the second message it went down. Since I'm not Bayeasian, I don't > know > what to say about the effect of my messages. > > Cheers, Jari Oksanen > > ______________________________________________ > r-h...@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide > http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code. -- Spencer Graves, PE, PhD President and Chief Operating Officer Structure Inspection and Monitoring, Inc. 751 Emerson Ct. San José, CA 95126 ph: 408-655-4567 ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel