Garrett D'Amore writes: > I think that the bug database needs to reside outside Sun.
I don't think that matters. The key issue is that everyone has equal access. > And I think > that it should not be duplicated into a private database inside Sun. > Otherwise Sun engineers will continue to just use the internal db and > not participate externally. I strongly agree with that. > Sun's bugster will need to stay around for various reasons, but there is > no reason for it to be necessary for continued use by Solaris engineers. > > This does mean some headache for those engineers which have to work on > internal only products (e.g. hardware bug tracking) _and_ also on > OpenSolaris bugs But I think they'll manage. Agreed; there'll be some upheaval. But the first issue is, as Keith Wesolowski mentioned, to get requirements for a bug tracking system (just as was done for source code management), and then select the system that best matches the requirements. If that's bugster (with timely fixes to make it open), that's fine. If it's something else, that's fine, too. But I don't think we ought to include or disinclude any particular solution based on who provides the infrastructure or on the history of how we got here. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
