Valerie Anne Bubb wrote:
On Wed, 26 Jul 2006, Scott Rotondo wrote:
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.
Development or not, making bugster accessible to the opensolaris
community does not go away. Our new found developers would still
like to track & fix bugs in OpenSolaris (post integration).
I would think our efforts on bugtracking would be better spent trying
to make a decent bridge to bugster & using the existing "development"
sandbox. It is very easy to move bugs from the "development" sandbox
to the normal part of the bugster database (product "solaris").
In fact, it is just a service request to the bugster team, who scripts
it for you, and little to no work for the development team.
Inside of Sun, I think we could all do with raising concerns on bugster
funding, outsourcing & interopterability with OpenSolaris.
Now, from my years of working with the bugster team with you, I realize
that
this is an uphill battle, but worth pursuing before we come up with
disjoint trackers that will make it a pain in the rear to move bugs
into the official database post integration (likely leading to
lost bugs)
I agree. I wasn't trying to suggest that we shouldn't continue with
trying to open up Bugster access. I was simply saying that I understand
why Stephen brought up the question about using other bug trackers.
Scott
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
