It's getting on my nerves
Again and again sourceforge seems to have problems with their CVS services - even if it is not their fault, but it is getting cumbersome.
Now i am sitting here, having over 100 modified files ready to be committed and not being able to since the 30th of march. Additionally we planned on releasing .20 the last weekend and now being planned for "when sf is up again". :/
If anyone is interested, the quote from the status page at sf.net:
(2006-04-03 05:55:21 - Project CVS Service) On 2006-03-30 the developer CVS server had a substantial system failure. Due to the implementation of the CVS service, there is a single point of failure with multiple points of recovery (there is more than one data source we could potentially recover from if there is any data loss as a result of the failure). This outage currently affects developer CVS access directly, but we have disabled tarball updates and data syncs from the developer CVS server to the anonymous pserver/ViewCVS hosts as an additional level of precaution. Our main focus since the outage was detected has been to safegaurd all data on the developer CVS server as well as possible. We are currently attempting to backup the data on the host, which is taking longer than we initially anticipated it would, but is a necessary step to fully safegaurd the host's data. Next, we are going to perform some data validation to ensure the data set appears valid. Pending successful completion of those steps, we'll reenable developer CVS access. A few days after, we'll reenable CVS tarballs and syncs to anonymous CVS. In the mean time, we're currently advancing plans for a CVS architecture change based upon the knowledge we gained during Subversion deployment to eliminate the single point of failure that developer CVS currently has, add horizontal scalability and overall service resiliance. However, we still do not have an estimate on when developer CVS services will be restored, but we have been, and currently are actively working to restore access to CVS. We appreciate your patience with us while we work to properly resolve this major outage.
The positive is of course my team is able to work locally on their sections, but we need to be careful about the commit order. ;)
posted by Acyd Burn @ 4/03/2006 04:16:00 PM
8 comments
links to this post
8 Comments:
sf is getting more and more annoying. I think during the last 2 weeks they were only for about 10 minutes *g* At least it feels this way to me ;) Esp. stupid if you have a milestone in a week (another project I'm affiliated with) and can't effectively merge the subprojects thanks to a dead CVS.
So is that why there hasn't been any updates recently?
Me, I haven't been keeping tabs with SF.net, and I also use Subversion, so I didn't know about the outage. Hopefully they'll get it fixed _soon_.
"(2006-04-03 14:04:56 - Project CVS Service) - As an update to the 2006-03-30 CVS outage, our current estimate is that CVS services will be back online (developer access) late Tuesday or early Wednesday (Pacific Timezone)."
Still rather annoying :(
"Additionally we planned on releasing .20 the last weekend and now being planned for "when sf is up again". :/"
are there security fixes involved in .20? If so, too bad.
Well, developer CVS is back, as DavidMJ was able to make a commit this evening. Although it's not being synced with pserver CVS at the moment, it's still something, and could mean that .20 could get packaged and shipped out.
Sadly, anonymous CVS sync is not yet restored, and - according to sf - it will be on friday. This also means that the snapshots will be out of sync, as well as people reporting bugs which are already fixed in CVS.
But hey, at least we are able to commit our changes. :D
Glad to see they finally opened back up partially, Im really excited about this next version of phpbb!
Just thought I would drop buy and say a personal Thank you Acyd burn!
After reading the latest update on annonymous CVS, I'm starting to have my doubts on anon CVS being back up tomorrow -- they seem to be having a lot more problems with the developer CVS, which, obviously, they have to fix.
Post a Comment
Links to this post:
Create a Link
<< Home