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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: Torsten Zuehlsdorff <mailinglists(at)toco-domains(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, 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 17:27:15
Message-ID: 27882.1443547635@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Corey Huinker <corey(dot)huinker(at)gmail(dot)com> writes:
>>> And they'd sure love to be in charge of our code repo.

>> Mh - i'm not a native speaker. I didn't understand this line.

> Tom was saying that the JIRA/Atlassian people would happily volunteer to
> host our code repository for no cost (in money) to us.

Not that so much as that the gitlab code really wants to be connected up
to our code repo. That makes complete sense in terms of its goals as
stated by Torsten upthread, namely to be a git repo manager. But it's
not what we're looking for here. We want an issue tracker, and we don't
particularly need it to decide that it's in charge of repo access
authorization for instance. There's a whole bunch of functionality there
that at best is useless to us, and at worst will get in the way.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-09-29 17:27:59 Re: CustomScan support on readfuncs.c
Previous Message Robert Haas 2015-09-29 17:19:19 Re: Parallel Seq Scan