Bugzilla bug tracking database for 2.5 now available.
The bugzilla database we proposed earlier is now available for use, hosted by OSDL.
Feel free to go ahead and create yourself an account, and log bugs in there. This is only for 2.5 bugs currently, and the main intent is to help us drive 2.5 into a timely and stable 2.6 (or 3.0).
Please let me or the supplied mailto URLs know of any problems you encounter, but please be patient with any inital teething problems and don't tell slashdot just yet ;-) Apologies for this not being ready quite at Halloween ... and there's not much data in there right now, but we'll keep feeding it over the coming few days, including importing Thomas Molina's list of bugs.
The categories probably need some more work, they'll evolve as bugs get logged. The reason I own huge numbers of subsystems is not just because I'm a derranged megalomaniac, it's more to do with the fact that I don't have other people available with accounts created to own them. Brave volunteers who've created an account would be most welcome, ideally the code maintainers for those subsystems, but other people familiar with those areas would be a great substitute. ;-)
M.
Quoted 8 lines · Martin J. Bligh
The bugzilla database we proposed earlier is now available for use, hosted by OSDL.
Feel free to go ahead and create yourself an account, and log bugs in there. This is only for 2.5 bugs currently, and the main intent is to help us drive 2.5 into a timely and stable 2.6 (or 3.0).
Fantastic, thanks.
If people have net driver bugs, feel free to report them to the above URL, and assign them to me...
Quoted 10 lines
Quoted 8 lines
The bugzilla database we proposed earlier is now available for use, hosted by OSDL.
Feel free to go ahead and create yourself an account, and log bugs in there. This is only for 2.5 bugs currently, and the main intent is to help us drive 2.5 into a timely and stable 2.6 (or 3.0).
Quoted 4 lines
Fantastic, thanks.
If people have net driver bugs, feel free to report them to the above URL, and assign them to me...
You should now be the default owner for net driver bugs. Still looking for other willing owners ;-)
M.
Quoted 5 lines · Martin J. Bligh
Quoted 2 lines
If people have net driver bugs, feel free to report them to the above URL, and assign them to me...
You should now be the default owner for net driver bugs. Still looking for other willing owners ;-)
Please assign the other networking categories to [email protected] thanks.
Em Thu, Nov 14, 2002 at 12:11:14PM -0800, David S. Miller escreveu:
Quoted 9 lines · Martin J. Bligh
Quoted 5 lines
Quoted 2 lines
If people have net driver bugs, feel free to report them to the above URL, and assign them to me...
You should now be the default owner for net driver bugs. Still looking for other willing owners ;-)
Please assign the other networking categories to [email protected] thanks.
Hey boss, if you accept I can take care of the ones for
net/{ipx,llc,appletalk,x25,lapb}
:-)
- Arnaldo
Quoted 7 lines
Quoted 7 lines · Martin J. Bligh
Quoted 5 lines
Quoted 2 lines
If people have net driver bugs, feel free to report them to the above URL, and assign them to me...
You should now be the default owner for net driver bugs. Still looking for other willing owners ;-)
Quoted 6 lines
Quoted 2 lines
Please assign the other networking categories to [email protected] thanks.
Hey boss, if you accept I can take care of the ones for
net/{ipx,llc,appletalk,x25,lapb}
We didn't bother breaking those out as they're .... ummm ... obscure, and I wasn't desperately keen to end up with 10,000 categories ;-) They should get dumped into "networking, other" at the moment. These are just the default owners, so bugs can just get reassigned to somebody else if that suits ...
M.
Em Thu, Nov 14, 2002 at 02:57:15PM -0800, Martin J. Bligh escreveu:
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines · Martin J. Bligh
Quoted 5 lines
Quoted 2 lines
If people have net driver bugs, feel free to report them to the above URL, and assign them to me...
You should now be the default owner for net driver bugs. Still looking for other willing owners ;-)
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
Please assign the other networking categories to [email protected] thanks.
Hey boss, if you accept I can take care of the ones for
net/{ipx,llc,appletalk,x25,lapb}
We didn't bother breaking those out as they're .... ummm ... obscure,
OK, I guessed that perhaps the reason for creating a category was if there was an active maintainer willing to actually look at the tickets for these a subsystem :-)
Quoted 1 line
and I wasn't desperately keen to end up with 10,000 categories ;-)
Agreed, do it as you're doing now or as when somebody explicitely asks because he maintains the thing and will work on respective tickets opened
Quoted 1 line
They should get dumped into "networking, other" at the moment.
No problem
Quoted 2 lines
These are just the default owners, so bugs can just get reassigned to somebody else if that suits ...
networking, other (or 'obscure' ;-)) can come to me, if nobody objects, I'll reassign if needed.
Just trying to find a way to help divide the load on the triage stage 8)
- Arnaldo
Quoted 4 lines
Quoted 1 line
and I wasn't desperately keen to end up with 10,000 categories ;-)
Agreed, do it as you're doing now or as when somebody explicitely asks because he maintains the thing and will work on respective tickets opened
Right. If we get a load on any one area, that should definitely be broken out as a subsection.
Quoted 11 lines
Quoted 1 line
They should get dumped into "networking, other" at the moment.
No problem
Quoted 2 lines
These are just the default owners, so bugs can just get reassigned to somebody else if that suits ...
networking, other (or 'obscure' ;-)) can come to me, if nobody objects, I'll reassign if needed.
Just trying to find a way to help divide the load on the triage stage 8)
Cool ... well one way to do that would be to take over "Networking, other" if everyone's OK with that. I wasn't anticipating much of a load on the more obscure networking stuff, but I'm proved wrong on a regular basis about so many things ... ;-)
M.
From: "Martin J. Bligh" <[email protected]>
Date: Thu, 14 Nov 2002 15:22:02 -0800
Quoted 1 line
Just trying to find a way to help divide the load on the triage stage 8)
Cool ... well one way to do that would be to take over "Networking, other" if everyone's OK with that. I wasn't anticipating much of a load on the more obscure networking stuff, but I'm proved wrong on a regular basis about so many things ... ;-)
Let Arnaldo take net/other, I'm totally fine with it.
Quoted 4 lines · Martin J. Bligh
The bugzilla database we proposed earlier is now available for use, hosted by OSDL.
I forgot to mention, it would IMO speed acceptance and increase usage if this was a vendor-neutral URL, like 'bugzilla.kernel.org'...
Jeff
Quoted 7 lines
Quoted 4 lines
The bugzilla database we proposed earlier is now available for use, hosted by OSDL.
I forgot to mention, it would IMO speed acceptance and increase usage if this was a vendor-neutral URL, like 'bugzilla.kernel.org'...
Though OSDL may be funded by a group of large companies, in practice they're vendor neutral for this sort of thing. I suspect any requests to Tim to remove all hardware categories that wasn't from vendor X, or anything equally ridiculous would just result in a hefty poke in the eye ;-) Also, I think it's polite to give them the recognition they deserve for hosting the site, and providing the machine in runs on.
I believe we have a common goal here ... to get 2.6 to be released in a timely fashion, and to be as stable as possible.
M.
Quoted 8 lines · Martin J. Bligh
Quoted 7 lines
Quoted 4 lines
The bugzilla database we proposed earlier is now available for use, hosted by OSDL.
I forgot to mention, it would IMO speed acceptance and increase usage if this was a vendor-neutral URL, like 'bugzilla.kernel.org'...
Quoted 7 lines
Though OSDL may be funded by a group of large companies, in practice they're vendor neutral for this sort of thing. I suspect any requests to Tim to remove all hardware categories that wasn't from vendor X, or anything equally ridiculous would just result in a hefty poke in the eye ;-) Also, I think it's polite to give them the recognition they deserve for hosting the site, and providing the machine in runs on.
I suspect that there would be blood on the Internet before that
sort of request would get through.
Of course a link from bugzilla,kernel.org is easy. :-)
Quoted 3 lines
I believe we have a common goal here ... to get 2.6 to be released in a timely fashion, and to be as stable as possible.
Works for me.
Quoted 7 lines
M.
-
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/
Signature · 5 lines
Timothy D. Witham - Lab Director - [email protected] Open Source Development Lab Inc - A non-profit corporation 15275 SW Koll Parkway - Suite H - Beaverton OR, 97006 (503)-626-2455 x11 (office) (503)-702-2871 (cell) (503)-626-2436 (fax)
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines
Quoted 4 lines
The bugzilla database we proposed earlier is now available for use, hosted by OSDL.
I forgot to mention, it would IMO speed acceptance and increase usage if this was a vendor-neutral URL, like 'bugzilla.kernel.org'...
OSDL is vendor neutral, by definition. Besides, we all know that Transmeta hosts ftp.kernel.org and Red Hat hosts vger (for varying definitions of "hosts", but you know what I mean). I do not see acceptance suffer, because we do not observe Transmeta or Red Hat pushing their agendas. Same with OSDL.
I'm more interested in contacting the admin to be a component owner for sparc, for instance. Someone is going to have a significant admin load, because Bugzilla is not going to be self-running. Who is that person?
-- Pete
Quoted 2 lines
I'm more interested in contacting the admin to be a component owner for sparc, for instance. Someone is going to have a significant
Not sure quite what you mean here ... if you want to volunteer to maintain a specific subsection, you can just email me or [email protected].
Quoted 2 lines
admin load, because Bugzilla is not going to be self-running. Who is that person?
I'm hoping to spread the admin load out amongst different people - one of the things for a system like this is that it's easier to scale it up by spreading the load. Anything that's not picked up by external people will have the slack picked up by some IBM people, to make sure the database doesn't end up as a fetid cesspit of festering stale misinformation ;-)
M.
Quoted 9 lines · Pete Zaitcev
Quoted 7 lines
Quoted 4 lines
The bugzilla database we proposed earlier is now available for use, hosted by OSDL.
I forgot to mention, it would IMO speed acceptance and increase usage if this was a vendor-neutral URL, like 'bugzilla.kernel.org'...
Quoted 5 lines
OSDL is vendor neutral, by definition. Besides, we all know that Transmeta hosts ftp.kernel.org and Red Hat hosts vger (for varying definitions of "hosts", but you know what I mean). I do not see acceptance suffer, because we do not observe Transmeta or Red Hat pushing their agendas. Same with OSDL.
Sure, but vger and ftp are both suffixed with "kernel.org" If Transmeta or Red Hat ever flake out, it's easier to redirect the domain to some other machine.
If nothing else it's consistent naming that keeps with the Principle of Least Surprise :)
Quoted 4 lines
I'm more interested in contacting the admin to be a component owner for sparc, for instance. Someone is going to have a significant admin load, because Bugzilla is not going to be self-running. Who is that person?
Check out Martin's original announcement, as well as his recent one. I'm pretty pleased: they have staff that will help triage bugs and keep the garbage level low. Hopefully leaving the kernel hackers to do nothing more than fix bugs :)
Jeff
Quoted 7 lines
Date: Thu, 14 Nov 2002 14:36:09 -0500
From: Jeff Garzik <[email protected]>[...]
Sure, but vger and ftp are both suffixed with "kernel.org" If
Transmeta or Red Hat ever flake out, it's easier to redirect the domain to some other machine.
You are right, I forgot about this aspect. My fingers typed "vger.rutgerds.edu" for a about a year, all by themselves.
Quoted 9 lines
Quoted 4 lines
I'm more interested in contacting the admin to be a component owner for sparc, for instance. Someone is going to have a significant admin load, because Bugzilla is not going to be self-running. Who is that person?
Check out Martin's original announcement, as well as his recent one. I'm pretty pleased: they have staff that will help triage bugs and keep the garbage level low. Hopefully leaving the kernel hackers to do nothing more than fix bugs :)
No, wait, I'm not talking about triage here, just admining the Bugzilla itself. I'll poke bugme-admin@ and see what comes out.
-- Pete
Quoted 2 lines · Pete Zaitcev
No, wait, I'm not talking about triage here, just admining the Bugzilla itself. I'll poke bugme-admin@ and see what comes out.
There _should_ be a live person doing that, but ping Martin as well if bugme-admin doesn't answer... :)
Quoted 7 lines · Martin J. Bligh
Quoted 2 lines
I'm more interested in contacting the admin to be a component owner for sparc, for instance. Someone is going to have a significant
Not sure quite what you mean here ... if you want to volunteer to maintain a specific subsection, you can just email me or [email protected].
Yep, that's what he meant (further clarified locally on IRC)... zaitcev->sparc32 bugs, and davem->sparc64 bugs.
Quoted 10 lines
Quoted 2 lines
admin load, because Bugzilla is not going to be self-running. Who is that person?
I'm hoping to spread the admin load out amongst different people - one of the things for a system like this is that it's easier to scale it up by spreading the load. Anything that's not picked up by external people will have the slack picked up by some IBM people, to make sure the database doesn't end up as a fetid cesspit of festering stale misinformation ;-)
I just re-assigned a bug, which generated a request in my mind: is there a default bug assignee besides you? :)
Jeff
Quoted 1 line
Yep, that's what he meant (further clarified locally on IRC)...
zaitcev->sparc32bugs, anddavem->sparc64bugs.
OK, I'll get that fixed up.
Quoted 10 lines
Quoted 9 lines
Quoted 2 lines
admin load, because Bugzilla is not going to be self-running. Who is that person?
I'm hoping to spread the admin load out amongst different people - one of the things for a system like this is that it's easier to scale it up by spreading the load. Anything that's not picked up by external people will have the slack picked up by some IBM people, to make sure the database doesn't end up as a fetid cesspit of festering stale misinformation ;-)
Quoted 2 lines
I just re-assigned a bug, which generated a request in my mind: is there a default bug assignee besides you? :)
The default assignee depends on the category you file into. I own a lot of them right now because there's nobody else to do it (though I have various volounteers now, so thats increasingly less true ...yay!).
M.
Would it be useful/desirable/possible to have a button in the defect to allow you to forward the important info about it to an email address? For instance, if I wanted to bring it to the attention of linux-mm?
That being said, I guess this should have been the first question:
Should bugs reported to bugme still be posted here (or elsewhere when appropriate)? I would assume so, at least for a while.
-Paul Larson
Quoted 3 lines · Paul Larson
That being said, I guess this should have been the first question:
Should bugs reported to bugme still be posted here (or elsewhere when appropriate)? I would assume so, at least for a while.
Yes!
The bugzilla database is a great idea but it should remain a database i.e. a list. Discussion and the initial reporting of bugs should remain on the relevant lists _please_.
Robert Love
Dear diary, on Thu, Nov 14, 2002 at 11:09:15PM CET, I got a letter, where Robert Love <[email protected]> told me, that...
Quoted 11 lines · Paul Larson
Quoted 4 lines
That being said, I guess this should have been the first question:
Should bugs reported to bugme still be posted here (or elsewhere when appropriate)? I would assume so, at least for a while.Yes!
The bugzilla database is a great idea but it should remain a database i.e. a list. Discussion and the initial reporting of bugs should remain on the relevant lists _please_.
What about using the bugzilla email gateway? While it would be feasible that bugs should be added through the web interface, why not to automagically forward changes (new comments, attachments, maybe also status?) to appropriate mailing lists and absorb the replies to the thread back to bugzilla as the new comments? Ok, this would require people to cut the Cc soon enough not to stack 100-messages thread slowly evolving to completely different topic into bugzilla ;-).
If there is an interest in this and noone else is overly keen to do it, I would be willing to investigate this and check the functionality of the email gateway in bugzilla's contrib/ and possibly extend/fix it for our usage.
Signature · 6 lines
Petr "Pasky" Baudis
.
weapon, n.:
An index of the lack of development of a culture.
.
Public PGP key && geekcode && homepage: http://pasky.ji.cz/~pasky/A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines
Quoted 3 lines
The bugzilla database is a great idea but it should remain a database i.e. a list. Discussion and the initial reporting of bugs should remain on the relevant lists _please_.
What about using the bugzilla email gateway? While it would be feasible that bugs should be added through the web interface, why not to automagically forward changes (new comments, attachments, maybe also status?) to appropriate mailing lists and absorb the replies to the thread back to bugzilla as the new comments?
Requestors and anyone with an account can add a list to 'cc' field, so updates will get to the list. As for gatewaying from lists to Bugzilla, I _strongly_ oppose it, and I hope DaveM would support me. It's a door for spam and nothing else. If you have no IP connectivity and read your linux-kernel with FIDO gateway and GoldED, use normal ways of cooperating with maintainers. Bugzilla is complimentary, not mandatory.
-- Pete
Quoted 7 lines
Requestors and anyone with an account can add a list to 'cc' field, so updates will get to the list. As for gatewaying from lists to Bugzilla, I _strongly_ oppose it, and I hope DaveM would support me. It's a door for spam and nothing else. If you have no IP connectivity and read your linux-kernel with FIDO gateway and GoldED, use normal ways of cooperating with maintainers. Bugzilla is complimentary, not mandatory.
Agreed - cc'ing lkml is just going to piss people off.
Possibly we could create a tree hierarchy of email aliases for people who want to watch certain categories at some point in the future, then people can opt-in as they please.
M.
Quoted 7 lines · Martin J. Bligh
Quoted 2 lines
I'm more interested in contacting the admin to be a component owner for sparc, for instance. Someone is going to have a significant
Not sure quite what you mean here ... if you want to volunteer to maintain a specific subsection, you can just email me or [email protected].
Yep, that's what he meant (further clarified locally on IRC)... zaitcev->sparc32 bugs, and davem->sparc64 bugs.
Quoted 10 lines
Quoted 2 lines
admin load, because Bugzilla is not going to be self-running. Who is that person?
I'm hoping to spread the admin load out amongst different people - one of the things for a system like this is that it's easier to scale it up by spreading the load. Anything that's not picked up by external people will have the slack picked up by some IBM people, to make sure the database doesn't end up as a fetid cesspit of festering stale misinformation ;-)
I just re-assigned a bug, which generated a request in my mind: is there a default bug assignee besides you? :)
Jeff
-
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/
Quoted 1 line · Martin J. Bligh
Please let me or the supplied mailto URLs know of any problems you encounter, but please be patient with any inital teething problems and don't tell slashdot just yet ;-)
Well, someone didn't listen....it's on slashdot.
Signature · 4 lines
Chris Friesen | MailStop: 043/33/F10 Nortel Networks | work: (613) 765-0557 3500 Carling Avenue | fax: (613) 765-2986 Nepean, ON K2H 8E9 Canada | email: [email protected]
Quoted 3 lines · Martin J. Bligh
Brave volunteers who've created an account would be most welcome, ideally the code maintainers for those subsystems, but other people familiar with those areas would be a great substitute. ;-)
If we can volunteer for sub-categories (I do not think so, but hey...) I will do "preemption" and "scheduler", if no one else has volunteered.
Otherwise I will take all of "Process Management", and the huge blanket of bugs that includes :)
Robert Love