I spoke with Scott and he had some very good points about publishing gems like right_popen, which contain native extensions.

Because of some Bundler issues, it is difficult to use these as gitted gems under Windows, meaning that we need to publish these gems somewhere to do end-to-end testing against RightLink. If we publish them to RubyGems.org, then we are publishing something we have not tested!

However, I still feel that it's important for us to commit to publishing our gems when we publish a package. We want to set a good precedent for RightLink as a product. (I fully expect that in RightLink 7.0 we will let people build their own packages, or maybe just use omnibus to build our packages.)

As a compromise, I propose the following:
-- For non-GA releases of RightLink, it is acceptable to use gitted gems or to publish gems to our private S3 bucket.
-- Whenever we produce a GA release of RightLink, we must build all corresponding gems and publish them to RubyGems.org