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

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Torsten Zuehlsdorff <mailinglists(at)toco-domains(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, Ryan Pedela <rpedela(at)datalanche(dot)com>, 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-30 07:10:42
Message-ID: 560B8AF2.9020206@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/29/15 12:46 PM, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> On 2015-09-29 13:40:28 -0400, Tom Lane wrote:
>>> I think you missed my point: gitlab would then believe it's in charge of,
>>> eg, granting write access to that repo. We could perhaps whack it over
>>> the head till it only does what we want and not ten other things, but
>>> we'd be swimming upstream.
>
>> We today already have a github mirror, where exactly the same thing
>> exists, no?
>
> Sure, there's a mirror out there somewhere. It has nothing to do with
> our core development processes.

There are APIs as well, so it could be driven that way. I suspect it's
unnecessary though.

BTW, the docs are at http://doc.gitlab.com/ce/.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message oonishitk 2015-09-30 07:15:19 Standby server crashes in master and REL9_5_STABLE branches
Previous Message Jim Nasby 2015-09-30 07:02:43 Re: No Issue Tracker - Say it Ain't So!