Text of discourse.matplotlib.org › t › new-issue-tracker-on-github › 15337 as Styx crawled it on Nov 20, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

New issue tracker on GitHub - matplotlib-devel - Matplotlib

New issue tracker on GitHub Development matplotlib-devel Michael_Droettboom April 11, 2011, 4:13pm 1 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.

Cheers, Mike ··· -- Michael Droettboom Science Software Branch Space Telescope Science Institute Baltimore, Maryland, USA _Darren_Dale2 April 11, 2011, 5:24pm 2 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. ··· On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom < [email protected] ...> 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: Issues 2.0: The Next Generation - The GitHub Blog The integration with git commits (closing issues by mentioning them in the commit message) is particularly compelling.

Paul_Ivanov2 April 11, 2011, 7:02pm 3 Darren Dale, on 2011-04-11 13:24, 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: > > Issues 2.0: The Next Generation - The GitHub Blog > > 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. I'm fine either way - though moving to GitHub certainly makes sense as it has momentum - whereas SF.net has been stagnating and not getting any faster for quite some time now.

My only concern / request is that we transfer and/or clean up (wholesale) the sf.net bug tracker before we move to GH. It'd be a disservice to our users if we just ignored or mass-closed those issues in the transition to GH. best, ··· On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom < [email protected] ...> wrote: -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 _Darren_Dale2 April 11, 2011, 7:14pm 4 I spent a weekend working on porting the issues to github.

GitHub - ddale/mpl-issues contains an xml dump of the sourceforge tracker, along with the script I used to parse the dump file, filter it, and upload the issues to that repo. It could be improved to add labels, assign to developers, assign milestones, once github provides API access to issues-2.0. ··· On Mon, Apr 11, 2011 at 3:02 PM, Paul Ivanov < [email protected] ...> wrote: Darren Dale, on 2011-04-11 13:24, wrote: On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom < [email protected] ...> 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: > > Issues 2.0: The Next Generation - The GitHub Blog > > 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. I'm fine either way - though moving to GitHub certainly makes sense as it has momentum - whereas SF.net has been stagnating and not getting any faster for quite some time now.

My only concern / request is that we transfer and/or clean up (wholesale) the sf.net bug tracker before we move to GH. It'd be a disservice to our users if we just ignored or mass-closed those issues in the transition to GH. Eric_Firing2 April 11, 2011, 7:51pm 5 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. Eric ··· On 04/11/2011 07:24 AM, Darren Dale wrote: On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom< [email protected] ...> 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: Issues 2.0: The Next Generation - The GitHub Blog 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. Michael_Droettboom April 11, 2011, 7:40pm 6 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: Issues 2.0: The Next Generation - The GitHub Blog 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. Labels could be used for that purpose -- but it would be "by convention", so I can imagine we'd forget to do that from time to time. (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.

I see this too. And I think we're not the only ones -- there's a bug filed about it: http://support.github.com/discussions/issues-issues/608-closed-tickets-do-not-show-up-in-the-list-firefox-36

The rest of this page is on the live site.