Re: Managing the community information stream

Поиск
Список
Период
Сортировка
От Joshua D. Drake
Тема Re: Managing the community information stream
Дата
Msg-id 4649F6F9.1070407@commandprompt.com
обсуждение исходный текст
Ответ на Re: Managing the community information stream  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: Managing the community information stream  (Bruce Momjian <bruce@momjian.us>)
Список 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 по дате отправления:

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: Not ready for 8.3
Следующее
От: Oleg Bartunov
Дата:
Сообщение: Re: Not ready for 8.3