From: Tom Copeland <tom@...>
Date: 2009-11-24T00:40:31+09:00
Subject: Re: RubyForge gem index is no more


On Nov 22, 2009, at 10:30 PM, Luis Lavena wrote:
> 
> Tom, I'm not arguing why the communication was in the background or
> not, I'm cool with Gemcutter and really like it.
> 
> The issue, from my PoV is other.
> 
> I've closed several bug reports and responded several emails about 500
> errors and 403 errors when installing gems.
> 
> Is not that these users didn't connect properly to the new server, but
> they had an older version of RubyGems as part of the combo with other
> issues that I couldn't replicate
> 
> A better heads up, not just for Ruby gem authors for community as a
> whole using channels like RubyForge, Ruby-Lang and Ruby-Talk would
> have been great.
> 
> Anyhow, canned a template answer with links to either my own posts and
> Gemcutter ones for the time being.
> 
> Thank you for your time answering my comments.

Luis, you're absolutely right, that's a hole in the new system - it doesn't generate yaml.Z and yaml, so old rubygem clients can't work with it.  And of course you're on the receiving end of complaints about that... you're right, that is a bummer.  I wonder if there's something we can do about that... maybe pull the gems off S3 and generate those old indexes once a week or something.

As you said, comms could have been better throughout this process.  Something for us to improve in the future,

Yours,

Tom