From: Yusuke ENDOH Date: 2010-07-13T12:38:32+09:00 Subject: [ruby-core:31236] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 Hi, 2010/7/13 Yukihiro Matsumoto : > I am sorry that I haven't followed this issue. As far as I > understand, this is caused by unfortunate timing. Eric was busy at > the critical timing Not only at that timing. He is always busy. [ruby-core:28689] [ruby-core:28781] [ruby-core:28926] [ruby-core:30127] [ruby-core:30129] [ruby-core:30130] [ruby-core:30151] [ruby-core:30189] [ruby-core:30456] [ruby-core:30619] [ruby-core:30621] [ruby-core:30792] [ruby-core:30907] Of course I can't blame his busyness, but looking objectively, he looks like ineligible for a maintainer. > I think 1.9.2 should run Rails3. I hope too. I wanted them to know the very poor maintenance status of rubygems and to do it themselves, as they are beneficiaries. OTOH there are also many people who wait for 1.9.2 but don't need rubygems nor rails. > If I understand what Yehuda told me > correctly, this issue could be a show stopper. I don't agree to see the issue as a show stopper unless some active developer is assigned to the issue. Otherwise it would take forever, literally. In practice, I think Evan's patch is a meeting point, if Roger can confirm the [BUG] does not occur on ruby_1_9_2 with Evan's patch. If it does not occur on ruby_1_9_2, I also suspect it is due to lazy sweep ([ruby-core:31228]). -- Yusuke Endoh