From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Vince Vielhaber <vev(at)michvhf(dot)com> |
Cc: | Justin Clift <justin(at)postgresql(dot)org>, Philip Warner <pjw(at)rhyme(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Link to bug webpage |
Date: | 2001-08-21 15:22:42 |
Message-ID: | 200108211522.f7LFMh705012@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > > Do you actually expect someone to go thru the 400+ items in the database
> > > and compare them to the TODO list? Seems to me that's something the
> > > maintainer of the TODO list would be doing. Can you point me to the form
> > > that gets something on the TODO list that the average user can use? Can
> > > you guarantee every bug will end up on the TODO list? Can you point me
> > > to the place on the TODO list when a user can look at to see if a bug has
> > > been fixed or even reported?
> >
> > I was just asking. If I have been missing stuff, I can see more value
> > to a bug database.
> >
> > > You're making more of an issue with all of this than there is. The TODO
> > > list has a purpose, as does CVS, as do the mailing lists, as does the
> > > regression database, as does the bugs database, as do the interactive
> > > docs, ...
> >
> > OK, what value does a bug database have over a TODO list?
>
> History. Searchability. Doesn't include features to be addeed.
Yea, they would be nice.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2001-08-21 15:26:20 | Re: [PORTS] mx.rpm |
Previous Message | Vince Vielhaber | 2001-08-21 15:20:36 | Re: Link to bug webpage |