+1 on this. I suggest that we not migrate issues from Jira directly, but rather ask the user community to open up tickets in Github for issues that are important to them, linking back to Jira. Tickets that don't have advocates will thus be abandoned.
On Thu, Feb 9, 2012 at 5:04 PM, Alister Scott <alister.sc...@gmail.com>wrote: > Plus we also get to link an issue to a push/pull request. > > Cheers, > > > Alister Scott > Brisbane, Australia > Watir Web Master: http://watir.com > Blog: http://watirmelon.com > LinkedIn: http://www.linkedin.com/in/alisterscott > > "There are two ways to get enough: One is to continue to accumulate more > and more. The other is to desire less." *~ G. K. Chesterton* > > > On Fri, Feb 10, 2012 at 8:25 AM, Hugh McGowan <colinsda...@gmail.com>wrote: > >> +1 >> >> I think it's a great idea and helps consolidate things. Seems like we >> should be able to lock folks out of reporting new issues and as long as we >> can go through history if needed we should be OK. I like the idea a lot >> >> Hugh >> >> _______________________________________________ >> Wtr-development mailing list >> Wtr-development@rubyforge.org >> http://rubyforge.org/mailman/listinfo/wtr-development >> > > > _______________________________________________ > Wtr-development mailing list > Wtr-development@rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > -- Bret Pettichord Director, Watir Project, www.watir.com Blog, www.testingwithvision.com Twitter, www.twitter.com/bpettichord
_______________________________________________ Wtr-development mailing list Wtr-development@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-development
