Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 3B81162698C for ; Mon, 16 Apr 2012 13:24:35 -0300 (ADT) Received: from 30.55.colo.spiretech.net ([69.168.55.30] helo=lists.commandprompt.com) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SJojA-0005dI-LS for pgsql-hackers@postgresql.org; Mon, 16 Apr 2012 16:24:34 +0000 Received: from clam (spinlock.commandprompt.com [69.168.55.30]) by lists.commandprompt.com (Postfix) with ESMTPA id 07F9970; Mon, 16 Apr 2012 09:24:23 -0700 (PDT) Received: from clam ([195.88.15.88] helo=clam) by assp.commandprompt.com with ESMTPS(AES128-SHA) (2.1.1); 16 Apr 2012 09:24:21 -0700 From: Alex To: Dimitri Fontaine Cc: Alvaro Herrera , Jay Levitt , Peter Eisentraut , Robert Haas , Tom Lane , Greg Smith , Pg Hackers Subject: Bug tracker tool we need (was: Last gasp) References: <20120409222359.GE30702@tornado.leadboat.com> <4F83FCB10200002500046D70@gw.wicourts.gov> <4F84D3A0.8010808@2ndQuadrant.com> <1334165303.25392.9.camel@vanquo.pezone.net> <28338.1334168965@sss.pgh.pa.us> <1334180206.25392.39.camel@vanquo.pezone.net> <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> Date: Mon, 16 Apr 2012 19:24:12 +0300 In-Reply-To: <878vhwnjhv.fsf@hi-media-techno.com> (Dimitri Fontaine's message of "Mon, 16 Apr 2012 10:55:40 +0200") Message-ID: <877gxf7ihf.fsf_-_@commandprompt.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Assp-Version: 2.1.1(11364) on assp.commandprompt.com X-Assp-Client-TLS: yes X-Assp-ID: assp.commandprompt.com m1-93463-11242 X-Assp-Envelope-From: ash@commandprompt.com X-Assp-Intended-For: pgsql-hackers@postgresql.org X-Assp-Original-Subject: Bug tracker tool we need (was: Last gasp) X-Pg-Spam-Score: -0.6 (/) X-Archive-Number: 201204/829 X-Sequence-Number: 206632 Dimitri Fontaine writes: > Alvaro Herrera writes: >> I've used Redmine a lot, as you know, and I only keep using it because >> it's a requirement at work. It is certainly not close to usable for >> general pgsql stuff. (Trac, which we used to use prior to Redmine, was >> certainly much worse, though). > > Same story here, still using redmine a lot, all with custom reports etc. > >> I can't say that it's all that slow, or that there's a problem with the >> code, or that the search doesn't work right (and I've never had a wiki >> edit disappear, either, and I've used that a lot). It's just the wrong >> tool altogether. > > It's indeed slow here, and I agree that's not the problem. Not the tool > we need, +1. I still fail to see how Redmine doesn't fit into requirements summarized at that wiki page[1], so that must be something other than formal requirement of being free/open software and running postgres behind (some sort of "feeling" maybe?) 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... -- Regards, Alex [1] http://wiki.postgresql.org/wiki/TrackerDiscussion