pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Greg Smith <greg@2ndQuadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Jay Levitt <jay.levitt@gmail.com>
Cc: Alex <ash@commandprompt.com>
Cc: Dimitri Fontaine <dimitri@2ndquadrant.fr>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Bug tracker tool we need
Date: Wed, 18 Apr 2012 00:01:19 -0400
Message-ID: <4F8E3C8F.8030301@2ndQuadrant.com> (raw)
In-Reply-To: <19323.1334720651@sss.pgh.pa.us>
References: <CA+Tgmoa75QujxzCZC+dj=0+JayGPhJD2kQMDBmbGmmq_HPgHxw@mail.gmail.com>
	<CA+TgmoZLWG=napMA-Fx4u8PTGDkY2CMz84LXAACsvhKRL+D2vg@mail.gmail.com>
	<4F84D3A0.8010808@2ndQuadrant.com>
	<CA+TgmoaN2wi85HVS-xuZkw9O6O_RmF4ovxX+=n6o2x6a1S2b-A@mail.gmail.com>
	<1334165303.25392.9.camel@vanquo.pezone.net>
	<28338.1334168965@sss.pgh.pa.us>
	<1334180206.25392.39.camel@vanquo.pezone.net>
	<CA+TgmoariJzLZ-9CfhF-Xwezk=UbmG_WUk5KydPYb8qFJzgkXw@mail.gmail.com>
	<1334350086.9019.16.camel@vanquo.pezone.net>
	<878vhyeqyq.fsf@commandprompt.com>
	<4F89ED6C.4030609@gmail.com>
	<87d379mwan.fsf@commandprompt.com>
	<1334540156-sup-2520@alvh.no-ip.org>
	<878vhwnjhv.fsf@hi-media-techno.com>
	<877gxf7ihf.fsf_-_@commandprompt.com>
	<4F8C93B2.1000503@gmail.com>
	<CABUev! Ew+9ZCC8eBQmWyjrmEyFFH=oBV{ h@ L <CA+TgmobGU2LfCdrmXG0DW9HbN5qXAx2Uvh2swrWs38b-qJR-CA@mail.gmail.com>
	<14172.1334716224@sss.pgh.pa.us>
	<4F8E3394.5040801@2ndQuadrant.com>
	<19323.1334720651@sss.pgh.pa.us>

On 04/17/2012 11:44 PM, Tom Lane wrote:
> At the same time, I think we'd likely be a lot better off squirting this
> data into bugzilla or another standard tracker, instead of building our
> own infrastructure.

Perhaps.  It just struck me that a lot of the custom bits needed here 
regardless could be built/added to the usual workflow bottom-up.  You 
don't have to assume that either a full tracker or something like my 
simple POC idea will show up at the end to get started.  Making goal #1 
involve just mining for the data that's already around and squirting it 
onto a web page would be a useful exercise, one that's likely to benefit 
any tracker adoption.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com



view thread (73+ messages)  latest in thread

Message-ID: <4F8E3C8F.8030301@2ndQuadrant.com>
Permalink:  ../4F8E3C8F.8030301@2ndQuadrant.com/
Also on:    postgresql.org/message-id/4F8E3C8F.8030301@2ndQuadrant.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: greg@2ndQuadrant.com, tgl@sss.pgh.pa.us, robertmhaas@gmail.com, magnus@hagander.net, jay.levitt@gmail.com, ash@commandprompt.com, dimitri@2ndquadrant.fr, alvherre@commandprompt.com, peter_e@gmx.net
  Subject: Re: Bug tracker tool we need
  In-Reply-To: <4F8E3C8F.8030301@2ndQuadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox