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
···
On Fri, Jun 24, 2011 at 4:02 PM, Eric Firing <efiring@...229...> 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.