Re: [HACKERS] bugs - lets call an exterminator!
I think it'd be not so difficult to extend our mailware (fts.postgresql.org) to handle bug-list. Actually, mailware has much more features, it's already has search/read, track features. Adding post is trivial. Developers (who actually fix a bugs) usually read mailing lists and reply's to BUG, which should be automatically go to corresponding bug-thread. Oleg On Tue, 21 Aug 2001, Tom Lane wrote: Vince Vielhaber [EMAIL PROTECTED] writes: Needs easy reporting of bugs - sent to bugs list easy lookup of previous bugs summary of fix or workaround detail of fix or work around little to no intervention of developers ability of developer to add comments That should sum it up. Check. We've had a couple of volunteers to keep the database up to date. Is it enough? I dunno, if I were to guess I'd have to look at previous experience and say probably not. AFAIR, we had *zero* people paying any attention to the state of the bug database up to now. A couple of people ought to make a big difference. Is implementing yet another bugtool going to be the solution? Probably not. Do I want to go for number six? No. If you're the man maintaining it then I'm certainly not going to tell you how to do your job. OTOH --- it does seem like a lot of people like Bugzilla. Might be worth at least a cursory look. Here's what I propose. The current tool has a form - we keep it. The current tool mails to the bugs list - we keep it. Those are both fine. How do we get feedback in the other direction, ie mailing lists to bug database? That's the $64 question in my mind at the moment. regards, tom lane ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly Regards, Oleg _ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] bugs - lets call an exterminator!
On Tue, 21 Aug 2001, D. Hageman wrote: On Tue, 21 Aug 2001, Vince Vielhaber wrote: In the seemingly hundreds of thousands of messages on the bug database topic I think I've come up with the following.. Solution.. Is implementing yet another bugtool going to be the solution? Probably not. Do I want to go for number six? No. The current tool has a form - we keep it. The current tool mails to the bugs list - we keep it. You are correct on implementing another bug reporting tool - why re-invent the wheel? Why not use the bugzilla project for bug tracking? I do believe it has a postgresql backend by now and if it doesn't - I am sure it will soon or would be trivial to make a backend and contribute it back. This tool has been popularized by Mozilla and RedHat ... saying that I am sure the couple of RedHat employees on the list wouldn't mind giving a hand with setup and what not (though they will have to speak for themselves on this issues). Everybody keeps saying bugzilla. What EXACTLY will bugzilla do for us that would make me want to learn it and install it? BTW, the current wheel was invented a year ago 'cuze nothing really fit what we needed. Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 56K Nationwide Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[HACKERS] bugs - lets call an exterminator!
In the seemingly hundreds of thousands of messages on the bug database topic I think I've come up with the following.. Needs --- easy reporting of bugs - sent to bugs list easy lookup of previous bugs summary of fix or workaround detail of fix or work around little to no intervention of developers ability of developer to add comments That should sum it up. Now some history.. Over the last couple of years we've tried a number (5 I think) of bug tracking packages. Either Marc or me or both have had to learn it, install it, get it going and the result has been the same - the maintainers don't want to update it, it's a pain in the ass to administrator, set up, etc. The current bugtool. After a bunch of these failures I asked for input on what was needed in a tool. Web input interface, ability to track the bug report, email notification to the bug list, email notification to the reporter of the bug. The current bugtool does this, however the maintainers don't want to close the reports. I'm not faulting them, they're doing their jobs by fixing the bugs and reporting them to the bugs list. Updating the database. We've had a couple of volunteers to keep the database up to date. Is it enough? I dunno, if I were to guess I'd have to look at previous experience and say probably not. But I don't want that to discourage anything or anyone. Realities PostgreSQL is growing by leaps and bounds. Ross pointed out this fact earlier today. A solution has to happen and it has to happen now. If a tool is to be adapted to this task it will be the one I'm most familiar with - the current one. Solution.. Is implementing yet another bugtool going to be the solution? Probably not. Do I want to go for number six? No. Of the ideas posted, these stick out: o Web input o Minimal staff involvement o Maximal mailing list reporting o History o Searchability Here's what I propose. The current tool has a form - we keep it. The current tool mails to the bugs list - we keep it. Rather than searching the bugs list for open bugs that may not even be open, the search tool will need to search not only the database but it needs to also search the archives. For now (until the 400+ are classified) the search should/will search the bugs mailing list rather than the database. Recruit more than two people to help update the bugs database. After the database is somewhat up to date, include it into the normal search mechanism. Now then.. The folks that actually fix things, will this suffice as a start to our shortcomingss? If not, what is missing?? If so, let me know and I'll implement this in the short term. Silence at this time is definitely NOT A GOOD THING!!! Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 56K Nationwide Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] bugs - lets call an exterminator!
Vince Vielhaber [EMAIL PROTECTED] writes: Now some history.. Over the last couple of years we've tried a number (5 I think) of bug tracking packages. Either Marc or me or both have had to learn it, install it, get it going and the result has been the same - the maintainers don't want to update it, it's a pain in the ass to administrator, set up, etc. The current bugtool. After a bunch of these failures I asked for input on what was needed in a tool. Web input interface, ability to track the bug report, email notification to the bug list, email notification to the reporter of the bug. FTR, we're using bugzilla for this and it works great. We're working on porting it PostgreSQL. ftp://people.redhat.com/dkl/ should contain a recent state -- Trond Eivind Glomsrød Red Hat, Inc. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] bugs - lets call an exterminator!
At 20:08 21/08/01 -0400, Vince Vielhaber wrote: In the seemingly hundreds of thousands of messages on the bug database topic I think I've come up with the following.. Your first pass needs to have a simple mail and web based ssystem for developers to at least close bugs. The CC idea is probably fine. You might even want to put an X-header in the mail message, then for each bugs list message automatically generate a footer with a web link to close the bug, or some such - a bit like the TIPs we get all the time. This way, a developer can go to any message relating to the bug, click on the link close it. This should also send off a message to the list etc. Also, to make the jobs of the volunteers easier, it would be good for each bug details page sho show a list of bugs mailing list trafic relating to the bug, sorted by inverse date order (or, better, sub-threads). Then we can look in the most recent two or three to check the status... Philip Warner| __---_ Albatross Consulting Pty. Ltd. |/ - \ (A.B.N. 75 008 659 498) | /(@) __---_ Tel: (+61) 0500 83 82 81 | _ \ Fax: (+61) 0500 83 82 82 | ___ | Http://www.rhyme.com.au |/ \| |---- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/ ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] bugs - lets call an exterminator!
Vince Vielhaber [EMAIL PROTECTED] writes: Needs easy reporting of bugs - sent to bugs list easy lookup of previous bugs summary of fix or workaround detail of fix or work around little to no intervention of developers ability of developer to add comments That should sum it up. Check. We've had a couple of volunteers to keep the database up to date. Is it enough? I dunno, if I were to guess I'd have to look at previous experience and say probably not. AFAIR, we had *zero* people paying any attention to the state of the bug database up to now. A couple of people ought to make a big difference. Is implementing yet another bugtool going to be the solution? Probably not. Do I want to go for number six? No. If you're the man maintaining it then I'm certainly not going to tell you how to do your job. OTOH --- it does seem like a lot of people like Bugzilla. Might be worth at least a cursory look. Here's what I propose. The current tool has a form - we keep it. The current tool mails to the bugs list - we keep it. Those are both fine. How do we get feedback in the other direction, ie mailing lists to bug database? That's the $64 question in my mind at the moment. regards, tom lane ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] bugs - lets call an exterminator!
On Tue, 21 Aug 2001, Vince Vielhaber wrote: In the seemingly hundreds of thousands of messages on the bug database topic I think I've come up with the following.. Solution.. Is implementing yet another bugtool going to be the solution? Probably not. Do I want to go for number six? No. The current tool has a form - we keep it. The current tool mails to the bugs list - we keep it. You are correct on implementing another bug reporting tool - why re-invent the wheel? Why not use the bugzilla project for bug tracking? I do believe it has a postgresql backend by now and if it doesn't - I am sure it will soon or would be trivial to make a backend and contribute it back. This tool has been popularized by Mozilla and RedHat ... saying that I am sure the couple of RedHat employees on the list wouldn't mind giving a hand with setup and what not (though they will have to speak for themselves on this issues). -- //\\ || D. Hageman[EMAIL PROTECTED] || \\// ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
