OK, I wasn't expecting much enthusiasm for bugzilla.On Sat, 12 Jul 2003 08:38:24 +0200 Kim Woelders <[EMAIL PROTECTED]> babbled:
Carsten Haitzler (The Rasterman) wrote:
On Tue, 8 Jul 2003 13:02:09 +0100 (BST) "Dhruba Bandopadhyay" <[EMAIL PROTECTED]> babbled:
Hello
I realise that the help with e16.6 is voluntary. However, having seen the recent explosion in bug reports on this list I'm beginning if it would be better to record them officially on some sort of bugzilla web client. This would save duplication and also prevent reports getting lost in the traffic. Or even a web page which updates records of bug reports. Just a thought.
sourceforge.
need i say more? (it has a bug tracking system and we use it already for cvs, www, etc.)
Ehmm, so, is that the preferred place to report bugs then?
Does anybody actually pay attention to the SF "Support Requests"?
These "Support Requests" seem to me to be a mixture of ancient stuff that should have been closed ages ago, simple questions, and bug reports for all kinds of different things (e16, e17, imlib, epplets, ...), most of which nobody has responded to.
Please correct me if I'm wrong, but AFAICS the thing is not even searcheable, which in my opinion means that it is close to useless.
I think that bugzilla is vastly more useful, and I use it myself to try to keep track of E16 issues reported here and there.
What am I trying to say? If possible, I think it would be a good
idea to set up bugzilla for E (for bugs, not for support). If not,
I think that we should either take the SF bug thing seriously, close obsolete items and respond to requests, or close it down entirely and make it clear that bugs and support questions should
go to the e-devel/e-users lists.
Now running off to hide somewhere for a while :-)
in my experience people don't USE bugzilla much - users just e-mail things in anyway - they never search for a bug that is similar to theirs before they post one... and to be honest - i don't pay attention to bugzilla stuff nor any of them - because i'm almost always at the stage of "making lots of new things i know have bugs and i really am not interested in people telling me what i already know" :) thus i've never found ti useful (not to mention bugzilla's interfaces is a bit of a PITA)
we also have a limit to how much we can run on e's website. i'd say it'd be more useful to really keep a text file somewhere with BUGS and list known ones - as they get resolved shuffle them elsewhere int eh file and mark them as resolved :) that way its 1. text, 2. searchable, 3. easy to use, 4. stays with the cvs code so u have your list of bugs along with the code :)
I think I will make BUGS for E16.
And, I still think it is silly to have the SF bug/support pages that nobody pays attention to. Most of the issues there would be better off posted to one of the mailing lists.
/Kim
------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
