From: Ryan Davis <ryand-ruby@...>
Date: 2011-01-20T07:26:41+09:00
Subject: [ruby-core:34624] Re: Importing rubygems 1.5.0 (release candidate) into trunk.


On Jan 18, 2011, at 21:22 , NARUSE, Yui wrote:

> But on our side, who live with ruby-trunk, we don't want to live with
> broken library.
> It makes our life worse.

There are no bugs so bad that we should throw process out the window.

That makes our lives worse too. 

Submitting a bug and/or patch to rubygems, having it properly vetted, applied, and tested against 1.8.7, 1.9.1, and 1.9.2 is not too much to ask.

We'll happily do all the heavy lifting to make sure that bugs are fixed and applied to cruby in a timely fashion.

> Moreover we run chkbuild, autotest for CRuby, so we want to keep the
> result enough clean.

I'd be happy to add chkbuild to our process, but I'm unfamiliar with it and it doesn't appear to be in the repo. If it is just an autotest-like thing... well, I'm using autotest :)

> If you can think rubygems in CRuby's repo as a stable branch, you and we can make acceptable policy.

Except that it isn't a stable branch. The last commit I had to roll out is evidence of that. Changing the encoding format of file IO on the source index is not stable branch engineering. It wasn't even discussed w/ us first.