On Wed, Aug 29, 2007 at 12:42:02AM -0700, Natalie Protasevich wrote:
>...
> Then I think bugzilla needs:
> adding more categories such as security,
"security" would be a flag like "regression", not a category.
> system calls (lots of
> implementation suggestions for posix and non-posix ones),
>...
Bugzilla is for tracking bugs, not for discussing possible
kernel features.
Tracking feature or implementation suggestions wouldn't make sense.
Consider e.g. that there are several people on linux-kernel who often
write what they think the kernel should do but who never write a single
line of code themselves. There's no value in tracking such stuff.
> improved searches - for sure, for example in addition to
> pre-cooked queries make possible using "raw" queries directly on sql,
> which will address misplaced bugs and will make categories more
> dynamic;
What do you have in mind?
I've always been able to do any search I wanted using the "Advanced Search"
of Bugzilla. Well, just checking, it seems the search for the new
"regression" flag could be made easier, but that's not a general problem.
But what could be improved in the database would be to fix the
charset problems for getting the RSS feeds working (#8774). ;-)
> recipe database, for standard debugging requests and procedures
> (serial console, getting sysreq traces, bisecting etc. - things to cut
> and paste)
Documentation makes sense, but it belongs into some place like the
kernelnewbies wiki, not the Bugzilla itself.
> user modifiable personal environment ("my bugzilla"), more of
> morph type interface around the database.
Preferences settings plus saved searches already work.
What is missing?
> ... not mentioning all flaws and problems with current one (cannot get
> back to home page,
There's a "Home" link that does exactly this among the actions offered
at the bottom of all pages.
> clear previous search,
There's a "Search" link that gives you a new search among the actions
offered at the bottom of all pages.
> do certain updates in one step
>...
The only thing that comes into my mind is that you cannot reassign a bug
and change it's status in one step. But "flaws and problems" would IMHO
be too hard an expression since it works fine with two updates.
> Regressions need to be tracked in effective manner, and I also noticed
> counter intuitive question that we have now (the infamous "last
> release when it _didn't_ happen") is clearly not the way to go, rather
> adding simple boxes "Was working in XX" and "Not working in XX" or
> similar straightforward question.
Sounds like a good solution for the one question so many submitters get
wrong. :-)
> In my opinion bugzilla is far from being a convenient tool. I suspect
> that hating bugzilla comes down to having to deal with no
> sophisticated interface that is inadequate - when so many nice and
> slick tools and sites are around that we all used to. I am also
> investigating and checking out other bugzillas looking for good ideas.
Bugzilla isn't that bad and it has the advantage of being the most
popular bug tracking system for open source projects, which means that
most likely every kernel developer and many submitters have already used
a Bugzilla at some other project.
>From past discussions my impression was that several kernel developers
have an email based workflow and are reluctant to integrate web based
actions into their workflow.
I'd say the success of any bigger Bugzilla change or switch to a
different or writing of a new bug tracking system could be measured
by answering the following question:
Will Linus Torvalds and David Miller use it?
> Thanks,
> --Natalie
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
