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

help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Alex <ash@commandprompt.com>
Cc: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Jay Levitt <jay.levitt@gmail.com>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Bug tracker tool we need
Date: Mon, 16 Apr 2012 16:01:39 -0700
Message-ID: <4F8CA4D3.6060008@commandprompt.com> (raw)
In-Reply-To: <877gxf7ihf.fsf_-_@commandprompt.com>
References: <CA+Tgmoa75QujxzCZC+dj=0+JayGPhJD2kQMDBmbGmmq_HPgHxw@mail.gmail.com>
	<4F83FCB10200002500046D70@gw.wicourts.gov>
	<CAEYLb_W3hOXQYGEA=aJCk-Y-7OFak4V7e3vT1y-XcMukGY3-tQ@mail.gmail.com>
	<CA+TgmoY+p8BiRPgCQQdON_a4DQvy3Hx03ug-j2eL8=Za_88WFQ@mail.gmail.com>
	<CAEYLb_VUiz57BeDy8d2gWQt_HRn9xpw83gt7MS0+wYmUopasrA@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>


On 04/16/2012 09:24 AM, Alex wrote:
> Jay, Alvaro, Dimitri (and whoever else wants to speak up) could you
> please describe your ideal tool for the task?
>
> Given that every other existing tool likely have pissed off someone
> already, I guess our best bet is writing one from scratch.
>
> Or maybe there isn't really a need for a tracker?  The core team have
> managed to live without one for so long after all...
I believe the biggest hurdle for many hackers is that in redmine, email 
is not a first class citizen. The majority of hackers are never going to 
want to go into a web interface to get something done, they live in 
VI/Emacs and the command line.

One thing that redmine definitely breaks is proper handling of 
attachments in email, thus the first thing moving to redmine would break 
would be patch submission.

JD


> --
> Regards,
> Alex
>
> [1] http://wiki.postgresql.org/wiki/TrackerDiscussion
>
>




view thread (73+ messages)  latest in thread

Message-ID: <4F8CA4D3.6060008@commandprompt.com>
Permalink:  ../4F8CA4D3.6060008@commandprompt.com/
Also on:    postgresql.org/message-id/4F8CA4D3.6060008@commandprompt.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: jd@commandprompt.com, ash@commandprompt.com, dimitri@2ndQuadrant.fr, alvherre@commandprompt.com, jay.levitt@gmail.com, peter_e@gmx.net, robertmhaas@gmail.com, tgl@sss.pgh.pa.us, greg@2ndquadrant.com
  Subject: Re: Bug tracker tool we need
  In-Reply-To: <4F8CA4D3.6060008@commandprompt.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