| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Managing the community information stream |
| Date: | 2007-05-15 18:07:53 |
| Message-ID: | 4649F6F9.1070407@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
>> In Debian's bug tracking system, when the bug is created (which is done
>> by sending an email to a certain address) it gets a number, and the
>> email is distributed to certain lists. People can then reply to that
>> mail, and send messages to 12345(at)bugs(dot)debian(dot)org and it gets tracked in
>> the bug, and you can see all those messages in the bug report. I
>> ass-ume that BZ 3.0 does something similar.
>
> But often a TODO item has multiple threads containing details (often
> months apart), and it isn't obvious at the time the thread is started
> that this will happen. Note the number of TODO items that now have
> multiple URLs. How is that handled?
Well you can certainly merge tickets, but one of the ideas would be to
help stop that :)...
Hey what about foo... oh we discussed that *here*...
Joshua D. Drake
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2007-05-15 18:11:48 | Re: Not ready for 8.3 |
| Previous Message | Andrew Dunstan | 2007-05-15 18:03:09 | Re: Not ready for 8.3 |