On Mon, Apr 11, 2011 at 3:51 PM, Eric Firing <efir...@hawaii.edu> wrote: > On 04/11/2011 07:24 AM, Darren Dale wrote: >> On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom<md...@stsci.edu> wrote: >>> I couldn't find the old thread about Sourceforge bug tracker vs. the >>> Github issue tracker, but maybe we should reevaluate based on the new >>> Github issue tracker announced on Saturday: >>> >>> https://github.com/blog/831-issues-2-0-the-next-generation >>> >>> The integration with git commits (closing issues by mentioning them in >>> the commit message) is particularly compelling. >> >> The new issue tracker is a really big improvement over the old github >> tracker, and I prefer it to the one at sourceforge since it integrates >> so nicely with github version control. The github tracker is still >> missing some features that we may want to consider: prioritize issues, >> add attachments, and perhaps report issues without opening a github >> account. > > It is better, but to my eye, still not good. > > Prioritization can be handled via labels or milestones, but the lack of > a simple, obvious attachment facility is a huge omission. As far as I > know there is also no simple set of categories for closed status--maybe > that would also be done with labels. (I'm not positive; I have not > closed an item, and nothing happens when I click the "60 closed issues" > tab, expecting to see the closed issues. Similarly, nothing happens > when I click the "submitted" "updated", and "comments" buttons. Maybe > all these things are bugs that show up if one does not have Firefox 4 or > Chrome?) The automatic, compulsory, irrevocable Markdown parsing of all > comments is a horrible design, and all the more so in the absence of > file up/download facility. > > It's being used; I think we are stuck with it. I have no objection to > getting the migration over with, if you have the machinery to do it, Dale.
I'm willing to continue working on the conversion, iff (not a typo) it is what the other developers want. It may be a while before I could get to it though. Darren ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
