On Fri, Jun 24, 2011 at 4:02 PM, Eric Firing <efir...@hawaii.edu> wrote: > >>> >>> Darren, >>> >>> I thought the Sourceforge tracker was supposed to be closed to new >>> entries >>> after your transition to github--is that not the case? >> >> Unfortunately, disabling the sourceforge tracker makes the links I >> created in the github issues unreachable. > > Then we have a real mess. Any ideas? Continuing with a couple hundred > issues duplicated in the two trackers, and with people still filing issues > in both, is completely unacceptable. I'm inclined to think that having gone > this far, we have to simply shut off the sourceforge tracker and accept the > loss of some information. As it is, conversation about issues that have > been transferred to github is effectively disconnected from the original > posters, without their having been notified. Ideally, all open issues on > sourceforge would be closed with a final comment noting the transfer to > github, but I suspect this is not feasible. > > You may switch any replies to matplotlib-devel if you like; maybe someone > else has an idea.
I'm working on a mass-closing of issues at the sourceforge tracker. I made a canned response that will direct to the github issues site. Darren ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
