Moore, Joe writes: > Keywords: boston-reviewed | boston-rr-doc | boston-waiver-approved | e1000g | > seabos-res-plan | seabos-rp-fix-s10u3 | seabos-sqo-reviewed | seattle-rr-doc > | seattle-waiver-list > -- Other than "e1000g", all of the keywords appear to be documenting the > workflow of moving this bugfix into Solaris, rather than OpenSolaris, and > certainly nothing that would match any sane keyword search for a problem I'm > having.
I'm afraid "keywords" aren't actually used in bugster (our bug tracking system) the way you might otherwise expect. Ordinary searches are done using full-text, as it's faster and more accurate to do that anyway, because ordinary mortals fail to identify the "right" keywords in all cases. Instead, "keywords" in bugster are used to group bugs together for special purposes, such as "all bugs affecting this platform" or "all bugs that need to be fixed in this release." They _intentionally_ have nothing to do with the bug contents, and are instead used for relational calculus. Of that list of "keywords," it's actually "e1000g" that's incorrect here. That's not a proper grouping, as the bug is *in* e1000g. > And finally, the crowning achievement of bug clarity: > Description: See Comments That's specifically not allowed. The person who did that was doing something incorrect with the bug system. There are several fields available in bugster for text; two of them are "Description" and "Comments." The description of the bug *MUST* go in the "Description" field. Anything else (with some rare security-related exceptions) is a usage error. The "Comments" are not displayed externally, and usually contain things like customer names, telephone numbers, and other such unrelated commentary. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
