On Jun 7, 2011, at 17:11 , Ryan Davis wrote: > I just activated github issues for rubygems and added a bunch of labels to > help us replicate the workflow from rubyforge's issue tracker (eg resolution, > category, and status). I've added a canned message to the 3 trackers we had > and mass blatted all open tickets to get the owners to migrate their tickets > to github issues. > > As such... there be noise.
Two weeks ago I announced that we were migrating to github issues. I gave everyone some time to move their tickets over so they'd be able to continue tracking them. I just reviewed the remaining tickets, manually transferred a few over and closed out the rest. I'm going to wait a while so that people can catch up with their email in case they missed my announcement and on Friday I'm going to turn off the trackers on rubyforge (I believe this only removes the links to the feature so everything should still work). So... That should be the end of the noise. _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
