Darren: > I don't see any mention of Trusted Extensions in this case so is the > assumption that TX is: > * not broken > * not enhanced in anyway > * all of the new functionality works in TX > > I'm particularly interested in the TX impact of GVFS given the use of D-Bus.
I seem to remember a funny story about Trusted Solaris. A while back there was a push to switch the default Trusted environment from Trusted CDE to Trusted Solaris. If we could EOL Trusted CDE then we could focus more resources on Trusted JDS and the future. Unfortunately there weren't any QA people assigned to Trusted Solaris, and there was some disagreement about which team should be responsible for resourcing such testing. Without QA testers to certify Trusted JDS we can not make the switch. So, Trusted CDE is still the default and we still divide our resources between the two Trusted environments. Ha ha. Pretty funny, right? I am not sure if those QA issues have been resolved yet. But I am sure that we will fix any bugs in the Trusted code that are reported, by QA or otherwise. I know that the Trusted JDS developer team actively works to fix issues they discover. However, without reasonable QA support, it is probably expected that bugs will slip through the cracks and get noticed by end users. I cc:ed the desktop QE team so they can respond about what Trusted testing is going on with JDS, and whether we've tested GVFS' usage of D-Bus with a Trusted Environment. If we haven't yet, I'd recommend we do such testing. Brian
