Stephen Hahn <[EMAIL PROTECTED]> writes: > I've made a number of edits, based on private feedback and the > on-alias responses. Clarifications: > > 1. My operational concern about access to the entire database was > specifically about not having a multi-gigabyte download. Nothing > else should be read into that point. > > 2. The relationship between the development branch and the > maintenance branches of any particular consolidation does not seem > well understood. It seems premature to conclude that a multiple > release relationship belongs in the community DTS, versus a > distribution's annotations. We can come back to this, perhaps as > some of the candidate evaluations proceed. > > 3. It's pretty much reality that it's going to take Sun time to > transition from one DTS to another; I would expect Sun is > obligated to develop tools of the kind Alan C meant, but I don't > believe that a Phase 2 scenario can be avoided, even with such > tools instantaneously materializing. > > 4. I would like to come back to Jim's point about "what DTSs do" > versus "what Bugster does" after we actually try one or two of > them. That is, unlike other evaluations, I think there's a > sandbox phase to the evaluation, where we agree that, say, a > notification alias is equivalent to both the IE and RM--or that we > don't agree, and need to formalize that ownership relation in our > requirements. (I suppose this point generalizes #2 above.) >
So, we seem to be getting nowhere here. Is anyone going to suggest other candidates (scarab? something else? are the mythical bugster people ever going to appear?). or are we left evaluating a "bugzilla or nothing" situation, as we are right now? This can't just be left on the floor, the current system is intolerably broken. -- Rich _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
