I brought this up before and I believe Eric said he'd watch both ticket systems (actually 3 counting the one for ruby itself). I think it makes sense only have one, migrate the tickets and kill the other.
On Sep 10, 2010 8:29 AM, "Luis Lavena" <luislav...@gmail.com> wrote: > On Tue, Aug 31, 2010 at 10:03 PM, Luis Lavena <luislav...@gmail.com> wrote: >> Hello, >> >> I was wondering which will the fate of RubyGems bug tracker at RubyForge. >> >> Also, is anyone getting any pull request for RubyGems?. >> >> Asking this due this interesting commit in a fork: >> >> http://github.com/gstark/rubygems/commit/483fdb5223a3c17e2b0ebb5dd02cb1e228498517 >> >> Which could provide some hint to users installing gems and misspelling them. >> >> There are comments there from authors of similar solutions. >> > > Bumping this message, anyone could care saying something (at least f*ck off). > > Thank you. > -- > Luis Lavena > AREA 17 > - > Perfection in design is achieved not when there is nothing more to add, > but rather when there is nothing more to take away. > Antoine de Saint-Exupéry > _______________________________________________ > Rubygems-developers mailing list > http://rubyforge.org/projects/rubygems > Rubygems-developers@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
