From: Luis Lavena <luislavena@...>
Date: 2010-09-11T03:55:12+09:00
Subject: Re: rubyforge <-> gemcutter issues

On Sep 10, 11:59 am, "ara.t.howard" <ara.t.how...@gmail.com> wrote:
> this is an issue gem publishers need to be aware off:
>
>  http://help.rubygems.org/discussions/problems/318-original-sync-to-ru...
>
> until it's fixed it's possible that your releases are not making it to
> other people's machines during 'gem install'
>
> fyi.

I never expected gems published on gemcutter (now rubygems.org) been
reflected at RubyForge automatically. Also, after the migration, never
expected gems (beyond .zip and tar packages) published at RubyForge be
feed into gemcutter.

The overhead of keep those things under sync is huge.

I disconnected gem publishing to RubyForge and now gems are pushed to
gemcutter only while .zip and tar to RubyForge for OS packagers.

That is what I understood and assumed.

FYI.
--
Luis Lavena