On Mon, Jun 20, 2011 at 2:33 PM, Eric Firing <efir...@hawaii.edu> wrote: > On 06/15/2011 10:35 AM, 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. > > Dale, > > I'm willing to go along with the transfer. Probably just as well to get > it over with now, assuming attached example files are included in some > usable fashion. As Mike notes, the sourceforge tracker is sluggish, > although in some ways it is better-designed.
Eric, Github's issue tracker still doesn't support attachements, so I've been inserting a hyperlink in the github issue to direct to the sourceforge issue, and I've included information at the bottom of the github issue concerning the history, which would indicate an attachment was submitted at sourceforge. Is that acceptable? Darren (Dale is my last name) ------------------------------------------------------------------------------ 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
