From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Steve Atkins <steve(at)blighty(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Learning curves and such (was Re: pgFoundry) |
Date: | 2005-05-18 05:59:48 |
Message-ID: | 87wtpxaxbf.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> What it comes down to is that a mailing list encourages many-eyes-on-
> one-bug synergy, whereas Bugzilla is designed to send a bug report
> to just one pair of eyes, or at most a small number of eyes. I haven't
> used RT but I doubt it's fundamentally different.
Actually RT is quite different. It's very closely tied to email. You get all
the updates in email and can respond to the emails and the results are
archived in the ticket.
However RT isn't really targeted at bug tracking specifically. It's more of a
trouble ticket system. Targeted largely to things like NOCs or incident
response ticketing systems.
It's much more flexible than pure bug tracking systems like bugzilla and might
be able to adapt to a more open email based working model better. But by the
same token it would take more attention to set it up and adapt it to bug
tracking.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-05-18 06:15:52 | Re: Learning curves and such (was Re: pgFoundry) |
Previous Message | Greg Stark | 2005-05-18 05:43:07 | Re: Cost of XLogInsert CRC calculations |