I'm working on a tool to help search, track and update bugs across the 
distro bug database (defect.opensolaris.org) as well as the various 
upstream bug databases that desktop and other FOSS software has to work 
with.

I would like to come up with a tagging convention so that if a distro 
bug is pushed upstream or closed as duplicate of an upsteam bug, we can 
still track it.  One example is the way some defect.opensolaris.org bugs 
are closed with "tracked in bugster."

I propose that the tag for a bug found in our distro and pushed upstream 
would retain:
   - An ID or link back to the original bug.
   - A unique OpenSolaris release tag  (So bugs found in OS2008.05 won't 
get mixed with bugs only in OS2008.11)

For upstream searching purposed, I think it would also be useful to 
retain this information:
   - Version control rev number of the module where the bug was found.
   - Architecture

I'm open to suggestions.  For example, which field of 
http://bugzilla.gnome.org should we use to indicate we pushed/duped a 
bug to them?  (As an alternative, we could keep an internal database of 
all bugs pushed upstream, but that could become difficult to manage)

I appreciate any suggestions.  Thanks!
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org

Reply via email to