Re: Managing the community information stream

Поиск
Список
Период
Сортировка
От Jim C. Nasby
Тема Re: Managing the community information stream
Дата
Msg-id 20070515222930.GU20707@nasby.net
обсуждение исходный текст
Ответ на Re: Managing the community information stream  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
On Tue, May 15, 2007 at 01:18:42PM -0400, 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?

Worst-case, for those cases we add URLs to the tracker manually like you
do now. The big advantage is that most of the time that's not needed.
And in cases where it's not automatic we can grant any number of people
permission to add that information to the tracker, because that
permission wouldn't be tied to CVS commit privs.
-- 
Jim Nasby                                      decibel@decibel.org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: 8.3 pending patch queue
Следующее
От: Russell Smith
Дата:
Сообщение: Re: [BUGS] Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped)