Scott Rotondo wrote:
John Levon wrote:
[snip]
The problem as I see it was using the "official" category rather than
what we
use: development/kernel/xen
Yes, it's very important to keep the development bugs (which are found
and fixed in a project-private workspace before integration) separate
from post-integration bugs (which really exist in the Solaris code base).
This is exactly why we created the "development" product in Bugster. It
keeps the development bugs separate and makes it easy to move any bugs
that remain open at integration time into the "solaris" product.
However, I'm concerned that Bugster may never be open enough to non-Sun
participants for it to be a viable choice for tracking OpenSolaris
project bugs.
Then I fail to see how project-specific bug trackers in any way solve this.
*projects* would get full use of a bug tracker disjoint from bugster,
and everyone would have 2 trackers (and N products) to search through
for bugs. Once projects integrated people on the outside would *still*
be screwed, as at that point CRs would migrate to bugster, or be filed
in bugster.
I'm currently not even close to sure that the benefit of this is worth
it (or, to some degree, whether it even exists).
-- Rich.
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
