On 06/15/2011 04:35 PM, Darren Dale wrote: > > I figured out how to migrate soureforges tracker to github issues with > the new github api. There are 232 open issues on the sourceforge > tracker, 79 of which are feature requests. Most sf issues are from > 2009 and on, many in the last few months. How do we want to handle > this? Migrate now and then cull the list at github? I can add a > sourceforge-import label that we can use to filter the list, closing > or assigning milestones and labels as we go, removing the sf-import > label once the issue has been inspected. Then we could disable the > tracker at the github site. Alternatively, we could try cull the list > at sourceforge first. Whatever you guys want to do.
My humble preference is to migrate them all to github with the special "SF" label. I find the github tracker (while not as full featured) faster to use. Cheers, Mike -- Michael Droettboom Science Software Branch Space Telescope Science Institute Baltimore, Maryland, USA ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
