Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!samsung!uakari.primate.wisc.edu!usenet.coe.montana.edu!warp.mhd.montana.edu!osynw From: osynw@warp.mhd.montana.edu (Nate Williams) Newsgroups: comp.unix.bsd Subject: Bug Report Format ? Summary: Need input. Keywords: Easy to understand, easy to find info. Message-ID: <1992Aug6.172338.22028@coe.montana.edu> Date: 6 Aug 92 17:23:38 GMT Sender: usenet@coe.montana.edu (USENET News System) Organization: Help me get some. Lines: 50 I would like to feedback on how to organize the Bug Report. I think I have the individual reports in a format that's readable, but what would be a good way to organize them. I have thought about organizing them by 1) Kernel bug fixed 5) Program bugs fixed 2) Kernel bug outstanding 6) Program bugs oustanding 3) System bugs fixed 7) Misc. bugs fixed 4) System bugs outstanding 8) Misc. bugs outstanding KERNEL is everything under /sys except the boot stuff. SYSYTEM is all the boot stuff, init, disklabel, .... PROGRAM is most everything under /usr/src MISC. is everything that's left, including setup bugs (tip), contributed software, additions, etc.... Another way I could format it is: FIXED bugs. OUTSTANDING bugs. Which might make it easier to find fixes. Also, what would be a good way to organize each sub group. Alpha- beticallly won't work, so what would be a good way to make it easier to find a certain kernel fix, other than looking at all the kernel bugs. Again, thanks to everyone who has sent in fixes. If I get some good feedback, I hope to get the first draft out before the weekend. (So people can fix ALL the bugs by Monday. :-) Nate -- osynw@terra.oscs.montana.edu | A hacker w/out a home. Anyone interested work: (406) 994-5991 | in a used Sys. Admin., with alot of home: (406) 586-0579 | good hacks left?