I promised myself I'd stay out of this discussion, but ...
Josh Berkus <j...@agliodbs.com> writes:
> I know we're big on reinventing the wheel here, but it would really be a
> better idea to use an established product than starting over from
> scratch. Writing a bug tracker is a lot of work and maintenance.
Yeah; "let's write our own bug tracker" is a good way to make sure nothing
comes of this. On the other hand, "let's get all the Postgres hackers to
change their habits" is an equally good way to make sure nothing comes of
this. (We tried that once already, with I-forget-which tracker; the
results were, um, forgettable.) I think the only approach that has any
chance of success is to connect up some existing tracker software to more
or less our existing work patterns. So somebody who wants to make this
happen needs to sit down and do that.
FWIW, I concur with the opinions that it needs to be an OSS tracker.
This project has been around for twenty years and I have every expectation
that it will survive for another twenty. I have no confidence in any
closed-source product still being available (and free) in 2035. We need
something with an active development/support community, too, so it doesn't
end up being us supporting it on our ownsome ten years out. Other than
that, I'm agnostic as to what gets picked.
regards, tom lane
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: