Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id F22EF16FA502 for ; Mon, 9 Jul 2012 16:26:53 -0300 (ADT) Received: from 30.55.colo.spiretech.net ([69.168.55.30] helo=lists.commandprompt.com) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SoJbd-00078q-IT for pgsql-hackers@postgresql.org; Mon, 09 Jul 2012 19:26:53 +0000 Received: from [192.168.1.5] (spinlock.commandprompt.com [69.168.55.30]) by lists.commandprompt.com (Postfix) with ESMTPA id 853BC48; Mon, 9 Jul 2012 12:26:36 -0700 (PDT) Received: from [192.168.1.5] ([68.118.161.194] helo=[192.168.1.5]) by assp.commandprompt.com with ESMTPS(AES256-SHA) (2.1.1); 9 Jul 2012 12:26:36 -0700 Message-ID: <4FFB306B.9000901@commandprompt.com> Date: Mon, 09 Jul 2012 12:26:35 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: Josh Berkus CC: pgsql-hackers@postgresql.org Subject: Re: Bug tracker tool we need References: <1334758503.29544.14.camel@vanquo.pezone.net> <20120706192141.GA11753@momjian.us> <20120706234626.GB26828@momjian.us> <20120707104851.GA525@svana.org> <20120707144211.GE26828@momjian.us> <20120707144805.GG26828@momjian.us> <4FFB2ADC.4040407@agliodbs.com> In-Reply-To: <4FFB2ADC.4040407@agliodbs.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Assp-Version: 2.1.1(11364) on assp.commandprompt.com X-Assp-Client-SSL: yes X-Assp-ID: assp.commandprompt.com m1-61996-04865 X-Assp-Envelope-From: jd@commandprompt.com X-Assp-Intended-For: josh@agliodbs.com X-Assp-Original-Subject: Re: [HACKERS] Bug tracker tool we need X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201207/405 X-Sequence-Number: 211088 On 07/09/2012 12:02 PM, Josh Berkus wrote: > > Hackers, > > So I want to repeat this because I think we are conflating several uses > for a "bug tracker" which aren't the same, and which really need to be > dealt with seperately. > > -- Better CF App: to track feature submissions, discussion, revisions > and reviews. > > -- Bug Submitter: easy-access way for users to submit bugs and check on > their status later. > =============== > -- Fix-Bug-Later Bug Tracker: a place to track bugs which are not > immediately fixable due to complexity/breakage/external > dependancies/priority. > > -- Fix Tracker: way for users to search if a particular issue was fixed, > and what release it was fixed in. =============== These two should be able to be the same piece of sotware. > > -- Testing Tracker: tool for user-testers to submit test reports for > development and beta releases. > This might be able to be the same piece as fix-bug-later... with a different front end. > The above are 5 different tasks with different requirements, and it's > far from clear that we want a new tool for all of them (or even want all > of them). > Not sure how to handle the first two. Bug submission is always a pita and although we could use the fix-bug-later app, it would clutter it as we were trying to determine real bugs vs user error. Sincerely, jD -- Command Prompt, Inc. - http://www.commandprompt.com/ PostgreSQL Support, Training, Professional Services and Development The PostgreSQL Conference - http://www.postgresqlconference.org/ @cmdpromptinc - @postgresconf - 509-416-6579