SourceForge.net CVS down again

What can I say? This sucks. You gotta read between the lines here, but a partial outage means no CVS access for developers, and the anonymous CVS access hasn’t been synced with the developer tree in about one and a half months. One wonders what is so partial about this. Seems to me like it is pretty complete.

Oh well. You get what you pay for, I suppose.

4 Comments

  1. Steve Loughran said,

    May 10, 2006 @ 20:55

    Yeah, I’m pretty unhappy too. I’m particularly unhappy about how the latest outage only got announced 2 days after it happened, like it took them that long to notice.

    then there was last month’s event, which first surfaced for us a week before it was announced, by a java file having the contents and history of a jsp page from an other project. A filesystem corruption if ever there was one. Yet despite us filing bugreps, nobody noticed or acted for a week, and even then, when the system came back up, our java file was still missing. I know, we are meant to back everything up locally, and we do grab the .tar image -but we got caught out by how they silently changed the naming scheme a few weeks earlier, so all our tars were out of date.

    The primary service sourceforge provides is open CVS and SVN repos. If they cannot keep them up and running, then there is no reason to go anywhere near them. We are certainly thinking hard about whether to host our own repo instead.

    -steve

  2. Wesslan said,

    May 11, 2006 @ 19:17

    Well, I know more than one project that has moved away from SF just because of its lack of services… :-(

  3. Colin Yates said,

    May 12, 2006 @ 15:02

    “Oh well. You get what you pay for, I suppose.” is probably not the best quote from an opensource developer :)

  4. Arjen Poutsma said,

    May 12, 2006 @ 15:10

    @Colin,

    You are right to point that out to me, though open source doesn’t necessarily mean gratis :-) .

RSS feed for comments on this post