On Jun 21, 2011, at 16:33 , Ryan Davis wrote:
> 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
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 bla
> As such... there be noise.
I think I pretty much speak for everyone when I say...
That's very much okay. :)
On Tuesday, June 7, 2011 at 8:11 PM, 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 i
On Tue, Jun 7, 2011 at 8:11 PM, 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
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 thei
