From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Bug tracker tool we need |
Date: | 2012-07-09 19:02:52 |
Message-ID: | 4FFB2ADC.4040407@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
-- Testing Tracker: tool for user-testers to submit test reports for
development and beta releases.
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).
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2012-07-09 19:26:35 | Re: Bug tracker tool we need |
Previous Message | Fujii Masao | 2012-07-09 18:23:58 | several problems in pg_receivexlog |