Re: unresolved bugs

Поиск
Список
Период
Сортировка
От Greg Stark
Тема Re: unresolved bugs
Дата
Msg-id 407d949e1001061645n4c067040y6e284c1c2eb61f2e@mail.gmail.com
обсуждение исходный текст
Ответ на Re: unresolved bugs  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: unresolved bugs  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: unresolved bugs  ("Joshua D. Drake" <jd@commandprompt.com>)
Список pgsql-hackers
On Wed, Jan 6, 2010 at 11:09 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
> Oh, wow, I didn't realize it was time for another round of this. Wheeeee!
>

Actually I suspect it is time.

My preferences have changed. While they used to go something like
debbugs > RT > nothing > bugzilla they now go something like debbugs >
RT > bugzilla > nothing. That is, even though bugzilla is possibly my
least favourite open source bug tracking system it's still better than
continuing the way we are. We've been pretty lucky so far, in part due
to Tom and others being remarkably diligent but it's only a matter of
time until we forget or miss a critical report. And from a PR point of
view it just looks terrible.

So in short while I still think debbugs is the best approach to this
I've seen at this point *any* free software based solution is fine
with me.

I'm assuming they can all be configured to send all new bug reports to
a mailing list and I do think we should choose one that stores the
database in Postgres, but I think that's true for nearly all of them
and can be made true for all of them.


-- 
greg


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

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: unresolved bugs
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Support ALTER TABLESPACE name SET/RESET ( tablespace_options ).