Re: Managing the community information stream - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Managing the community information stream
Date
Msg-id 4649F6F9.1070407@commandprompt.com
Whole thread Raw
In response to Re: Managing the community information stream  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Managing the community information stream
List 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@bugs.debian.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

> 



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Not ready for 8.3
Next
From: Oleg Bartunov
Date:
Subject: Re: Not ready for 8.3