Stephen Hahn writes: > Yes, and various Sun-specific steps we took during the DSCM change > have been completed/accepted for this change. So, if it's any > reassurance, it's getting to be more and more official. But I guess > what's being asked for is a complete picture, which I don't personally > have (beyond believing that we're in the two systems phase mentioned > in the DTS requirements).
More concretely, I think Rich is worried about what happens to ON and SFW gatelings who attempt to file an RTI based on a d.o.o entry. It'll "fail" in that webrti won't accept the defect number as valid, but "hg nits" and "hg pbchk" will blindly allow those numbers. I think that's actually a good state to be in. I suppose you could have a "are we allowed to use d.o.o yet?" flag somewhere, but I'd rather not. It just makes the external webrti application harder to deploy -- because users will be annoyed by the Cadmium commands. In other words, until webrti is finally fixed, you're still on the hook to do whatever is right by your local gate. Cadmium (and wx before it) can _help_ you do that, but they're hardly infallible. Thus, I'd prefer to build in the d.o.o support as soon as practical. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
