Thanks to Danek, we now have a shiny new Bugzilla closed resolution
field: TRACKEDINBUGSTER.  The intent of this is to mark bugs which have
a corresponding Bugster CR available.

Since tracking bugs via Bugster only makes sense for those components
whose fixes will be delivered through Nevada, this resolution should
obviously not be used for anything Indiana-specific such as bugs
related to Caiman, IPS, the Device Detection Utility, etc.

This evening, I closed a half dozen or so bugs with this resolution and
at the same time, I added to each bug's Whiteboard field a string of
the form

        BugsterCR=6696145

For Sun folks who end up using this resolution field on bugs reported
from outside of Sun, please provide a comment asking if the Reporter
would like to be added to the Interest List of the corresponding
Bugster CR, especially since http://bugs.opensolaris.org is not as rich
of an interface as Bugzilla by any means.  Also, please provide any
additional details in the Bugster CR's Description field as appropriate
from the Bugzilla bug.

I've begun discussing with the Solaris Bugster folks the best of
annotating the Bugster CRs in the reverse direction and we'll implement
something along those lines.  For now, adding a URL in the Description
field when appropriate seems reasonable.

Also, we'll try to indicate as we resync with each Nevada build going
forward which TRACKEDINBUGSTER issues have been resolved.

dsc
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to