From: Evan Phoenix Date: 2010-07-13T15:03:22+09:00 Subject: [ruby-core:31241] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 On Jul 12, 2010, at 8:38 PM, Yusuke ENDOH wrote: > 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. Now that I have been appointed gem_prelude maintainer, my hope is that this will no longer be an issue. > > >> 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. We must not overlook users of rubygems and rails on 1.9.2. In the US as well as europe, almost all ruby users use rubygems and significant percentage also use rails. I hope to use my presence to aid in rubygems maintenance status for 1.9.2 going forward. > > >> 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. As an open source developer, I agree that an issue can only be a show stopper if there are active developers assigned to it. This is why I have become much more active in helping to resolve this situation. > > > 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]). I am happy to hear that we are getting close to figure out the source of the GC bug. Please let me know whatever I can do to help get my patch into 1.9.2. Thank you. - Evan > > -- > Yusuke Endoh > >