I'm actually for some form of bug database. You're going to have problems like those described regardless of what system you use. At least with a bug database, things are a bit more transparent. You also gain features like email notification when a bug is updated, fixed, etc. It's much easier for an end user to report a bug and then be notified when the bug is resolved. It just takes some time for a developer to mark a bug fixed once they get it fixed. With a text file and this mailing list we are making the problem more manual and difficult to manage for both end users and developers. I don't have the experience that these other guys have, but I'd be willing to help manage a bug database if we moved in that direction. I think bad bug trackers are just indicators that nobody is managing the bugs. I would think that if there was some one dedicated to managing the database, that sort of problem won't happen.
As another note, it wouldn't be that hard to leverage Sourceforge's capabilities to track the bugs. // Dean Glazeski On Fri, Oct 23, 2009 at 2:13 AM, Holger Freyther <ze...@selfish.org> wrote: > On Friday 23 October 2009 08:56:04 Øyvind Harboe wrote: > > > What's wrong with just keeping a buglist in a text file > > > and whittling it down? Other than the fact that nobody > > > seems to be whittling our current one down much. > > > > I'm just doing a poll to see what direction the community > > wants to go. Not much excitement about this one it > > seems :-) > > > > Hi, > I agree with David. My experience with public bug trackers are horrible and > having a text file in the source might be good enough. > > E.g. OpenOCD is a developer tool and users experiencing a bug should be > able > to triage the bug until it is in a state it can be listed in the text file > and > send a patch to add it (or a patch to fix it). > > holger > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development >
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
