On Tue, 28 Aug 2001, Tom Lane wrote:
> Thomas Lockhart <[EMAIL PROTECTED]> writes:
> > The fundamental problem with bug tracking has been that the available
> > tools do not fit with our obviously successful mailing-list centered
> > development process. I certainly would consider it a distractio
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> The fundamental problem with bug tracking has been that the available
> tools do not fit with our obviously successful mailing-list centered
> development process. I certainly would consider it a distraction to
> consult that tool to be able to partici
*whimper* I've been out of town for a week, and will not be able to
catch up with ~2000 email messages. So I can't even get to the end of
this thread. But I must agree that PostgreSQL development is pushing the
limits of what a person can keep up with.
> I am not interested in finding a mailing l
Matthew T. O'Connor volunteered:
> I don't know what a kibo is, but I would be willing to put in some time
> helping maintaing a bug reporting system. One of the helpful things with
> bugzilla setup with some other big projects is that the bug gets assigned
to
> a developer and the bug submitter
Jan Wieck wrote:
>
> mlw wrote:
> > Has anyone thought of using Bugzilla? (It is MySQL based, of course) but it
> > might answer the bug database issues. (If you guys want a bug database)
>
> Bug tracking software that doesn't use transactions and
> referential integrity in a multi
mlw wrote:
> Has anyone thought of using Bugzilla? (It is MySQL based, of course) but it
> might answer the bug database issues. (If you guys want a bug database)
Bug tracking software that doesn't use transactions and
referential integrity in a multiuser environment? Sounds like
Has anyone thought of using Bugzilla? (It is MySQL based, of course) but it
might answer the bug database issues. (If you guys want a bug database)
RedHat has a version which can use Oracle, but it seems there is a file:
ftp://people.redhat.com/dkl/pgzilla-latest.tar.gz that my be interesting.
I know I am not on the kernel team, but I have been a software developer for
almost 20 years. ;-)
A bug database is a useful tool IF it has been setup to be so. If it is a
bare bones repository for bug reports it will not work. People won't use it.
A "good" bug database, i.e. one which will be u
Philip Warner wrote:
> I don't think this is a good solution. We really do need a list of bugs.
We
> probably need to list status and the releases they apply to.
Bugzilla can do this -- it has the concept of a Milestone and a Version.
> I don't think anybody but the most naieve (or biased) user
On Tue, 21 Aug 2001, Colin 't Hart wrote:
> We could install the Postgres version of Bugzilla.
> Yes, there's a version that runs on Postgres rather than MySQL.
> That way we don't have to maintain the bug system.
And how does it know when bugs are fixed?
Vince.
--
We could install the Postgres version of Bugzilla.
Yes, there's a version that runs on Postgres rather than MySQL.
That way we don't have to maintain the bug system.
> Ok the functionality as well as the menu item are gone. You do realize
> it's going to give the impression that we're trying to
11 matches
Mail list logo
