{"id":4731,"date":"2013-01-29T09:53:36","date_gmt":"2013-01-29T08:53:36","guid":{"rendered":"http:\/\/daniel.haxx.se\/blog\/?p=4731"},"modified":"2013-01-29T09:53:36","modified_gmt":"2013-01-29T08:53:36","slug":"the-new-bug-tracker-on-sourceforge","status":"publish","type":"post","link":"https:\/\/daniel.haxx.se\/blog\/2013\/01\/29\/the-new-bug-tracker-on-sourceforge\/","title":{"rendered":"the new bug tracker on sourceforge"},"content":{"rendered":"

A while ago Sourceforge<\/a> gave me the offer to upgrade curl’s bug tracker to “the new one” they offer. They do offer some arguments to why you would want to do this but they don’t elaborate much on the transition for existing projects. Since I’ve been annoyed and disappointed on the old one for years I decided to dive right in. I decided to post this blog entry to possibly encourage others as well, or at least explain how upgrading worked for us.<\/p>\n

I’ll start by explaining a bit about what’s so bad about the old Sourceforge bug tracker. Anyone who has tried to use it for anything “real” most likely already know about these things and then I figure my list can be used for a comparison if we’ve gotten annoyed by the same things.<\/p>\n

    \n
  1. They use a global bug id which makes all bug entries get very large numbers that aren’t in sequence and are fairly hard to remember.<\/li>\n
  2. You can’t respond to bug reports by mail, so you are forced to use the heavy ad-filled web site.<\/li>\n
  3. Ridiculous URLs to the bug tracker and each individual bug entry. I created a bounce CGI years ago on the curl web site to avoid having to use the overly long ones anywhere.<\/li>\n
  4. When sending out email notifications, it prepends the new comments while having the older ones below which basically is an odd-order top-posting style a lot of people and projects have a hard time to get accustomed to.<\/li>\n<\/ol>\n
    The new tracker\u00c2\u00a0addresses\u00c2\u00a0all of these issues and I agreed to allow it to make curl use their new tracker. And this is the outcome:<\/div>\n
    \n