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:
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
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:
(Hmm... git doesn't use its own issue tracker for tracking its own issues... what does that say? <wink>)
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,
The Wikis on github support a handful of formatting languages, including reStructuredText (which is what my fingers know best) -- so they "have the technology" to do something else. But honestly, for short issue comments, I think plain text is the best choice.
and all the more so in the absence of
file up/download facility.
They've got gist, of course, but it is neither easy or intuitive for casual use.
On 04/11/2011 03:51 PM, Eric Firing wrote:
On 04/11/2011 07:24 AM, Darren Dale wrote:
On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom<mdroe@...31...> wrote:
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.
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now! http://p.sf.net/sfu/ibm-webcastpromo
Matplotlib-devel mailing list
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA