Re: No Issue Tracker - Say it Ain't So!

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Ryan Pedela <rpedela(at)datalanche(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, David Fetter <david(at)fetter(dot)org>, YUriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: No Issue Tracker - Say it Ain't So!
Date: 2015-09-29 03:54:41
Message-ID: 18274.1443498881@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Jim Nasby (Jim(dot)Nasby(at)BlueTreble(dot)com) wrote:
>> 2 years ago is when they first released the enterprise edition,
>> which according to [1] had "The most important new feature is that
>> you can now add members to groups of projects."

> It needed a lot more than a single feature.

Just going to their primary web page, and noting that the first line gives
links to "Features" and "Pricing" (but not "Documentation"), and the
second line makes it clear that there's a big difference between the
"Community Edition" and the "Enterprise Edition", is already enough to
turn me off. We've seen that model before (mysql...) and it doesn't bode
well in the long run.

Further poking shows no evidence of any decent email integration, to name
just one of the things that have been mentioned as requirements in this
thread. On the other hand, they are big on LDAP logins, and even
two-factor authentication. (We need this for an issue tracker that's
supposed to provide visibility and easier reporting to people outside the
project?) And JIRA integration, which seems to be an anti-feature to some
on this thread. And they'd sure love to be in charge of our code repo.
And the main, possibly only, metadata they can track about an issue is
"assignee" and "milestone".

I can't imagine that this is what we want.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2015-09-29 04:39:14 Re: Parallel Seq Scan
Previous Message Pavel Stehule 2015-09-29 03:45:53 ToDo: possibility to set sqlcode, detail, hint in elog like functions in plpython and plperl