Re: No Issue Tracker - Say it Ain't So! - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: No Issue Tracker - Say it Ain't So!
Date
Msg-id 20150929021843.GB3685@tamriel.snowman.net
Whole thread Raw
In response to Re: No Issue Tracker - Say it Ain't So!  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: No Issue Tracker - Say it Ain't So!
List pgsql-hackers
JD,

* Joshua D. Drake (jd@commandprompt.com) wrote:
> On 09/28/2015 03:40 PM, Alvaro Herrera wrote:
> >We already made a similar choice some years ago when we started
> >depending on the then-recently open sourced SourceForge code for
> >pgFoundry.  That didn't turn out all that well in the long run.
>
> I think we need to look at long standing FOSS projects with a large
> and extended user base (Redmine, RT). Anything that is fairly
> community specific (Debbugs) likely will cause more heartache than
> it is worth in the long run.

debbugs is being used by Debian, and has been since before our first
release (I believe- according to wikipedia, it started in 1994..).
Further, it's now being used by the GNU project for things as important
(well, to some ;) as Emacs.

It also requires a minimum of customization to integrate with our
existing workflow.

That's good enough for us to at least test it out, in my view.

I've run both Redmine (ugh) and RT (it's good, but I don't feel it's
quite as good as debbugs, for us).

Further, to your specific point, neither of those have the kind of FOSS
community backing that debbugs has.  I have no issue with BestPractical
but I don't know that there's 100 individuals ready to jump in and help
keep RT going if they go south.  Redmine seems a bit better in that
regard, but it's painful to maintain and is only 9 years old, while
debbugs is old enough to drink in the US at this point.

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: No Issue Tracker - Say it Ain't So!
Next
From: Kouhei Kaigai
Date:
Subject: Re: [Proposal] Table partition + join pushdown