Does anybody want to update our release scripts to update the gemcutter index? I'm not too familiar with gemcutter yet. It is only a matter of adding "gem push" ?
alex ---------- Forwarded message ---------- From: <[email protected]> Date: Sat, Nov 21, 2009 at 7:17 PM Subject: [RubyForge] Gem index has been shut down To: [email protected] Hello - You're receiving this email because you're a RubyForge project admin and a recent change probably affects you. A few days ago we repointed gems.rubyforge.org to the gemcutter.org box. This means that Nick Quaranto's excellent gemcutter app is now indexing and serving all the gems - so rather than having two gem indexes, we now have one. As a consequence of this, when you release files to RubyForge you will probably also want to do a "gem push" to get them onto gemcutter and into the main gem index. Note that you can continue to release gems (and other files) at RubyForge; it's just that gems won't automatically make it into the main gem index. Yours, The RubyForge support team http://rubyforge.org/projects/support/
