From 4b6c0e31385f5f27a151088c0a2b614495c4e589 Mon Sep 17 00:00:00 2001 From: Paul Duncan Date: Thu, 14 Oct 2021 12:47:50 -0400 Subject: initial commit, including theme --- content/posts/2005-05-28-bugs-you-got-em-i-fix-em.html | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 content/posts/2005-05-28-bugs-you-got-em-i-fix-em.html (limited to 'content/posts/2005-05-28-bugs-you-got-em-i-fix-em.html') diff --git a/content/posts/2005-05-28-bugs-you-got-em-i-fix-em.html b/content/posts/2005-05-28-bugs-you-got-em-i-fix-em.html new file mode 100644 index 0000000..c2be5b9 --- /dev/null +++ b/content/posts/2005-05-28-bugs-you-got-em-i-fix-em.html @@ -0,0 +1,9 @@ +--- +date: "2005-05-28T19:37:08Z" +title: 'Bugs: You Got ''Em, I Fix ''Em' +--- + +

+I've tried to keep track of bug reports and feature requests via email, and it's just not working. So I gave up and set up a bug tracking page at http://bugs.pablotron.org/. Thomas (redshift) and I went through a handful of them, including Bugzilla (too much of a hassle to configure, pain in the ass to use), Flyspray (klunky user interface), Mantis (no easy anonymous view), CVSTrac (only one project per repository? gee, that's useful), and finally settled on PHPBugTracker, which does what I need and annoys me less than the rest. I also read this semi-dated article on bug trackers; I didn't pay much attention to the rank he gave each tracker, but it is a nice list of bug trackers out there. +

+ -- cgit v1.2.3