This post originated from an RSS feed registered with Ruby Buzz
by Daniel Berger.
Original Post: Quick gem indexing backfires (on me)
Feed Title: Testing 1,2,3...
Feed URL: http://djberg96.livejournal.com/data/rss
Feed Description: A blog on Ruby and other stuff.
In the dark ages of, oh, three months ago or so, it used to be that it could take up to an hour for a gem to be indexed by RubyForge. Tom Copeland improved the gem indexing process so that it now only takes up to five minutes. Most of the time that's a good thing - people can start using the new gem almost as soon as its uploaded.
Unfortunately, this improvement worked against me recently. When I released win32-api 1.3.0 I botched the original gem somehow (I can't remember now what I did), but it was something stupid and minor, so I deleted the old gem and uploaded the fixed gem without bumping the version. In the past I had up to an hour to notice and fix my mistake before any damage was done. That's not true any more.
Regrettably, it seems some of the Watir folks picked up the old gem before I uploaded the new one, causing unknown quantities of grief. Ugh.
I now have the dubious distinction of having the first "Gem Recall". Lovely.
Previous Topic
