Thanks, Steve, for collecting all of this! On Fri, 6 Apr 2007, Stephen Lau wrote:
> > Fields discussed as not being appropriate for publication were: > Evaluation, & Comments - both fields tend to contain confidential or > proprietary information. There was some discussion that we have had a notice > that Evaluation should not contain confidential information for years now - > and that we should work on opening this field (either through the use of > explicitly tagging a bug as Evaluation-publishable via a keyword, or doing a > product/cat filter). But in the interest of making the next Bugster release > (in April), Evaluation will be pushed back and revisted for the next > quarterly release (August). I don't think we were targeting the April release - I believe that's scheduled for the next week or so, which will not be enough time to follow up on some AIs, design, code & test. This is being targeted to the August release, IIRC. I know there were core issues that still needed to be investigated by the core team, such as: what level could we filter on (ie could we just do this by product level, or could we do more fine grained & exclude specific categories or subcategories). Hopefully that won't take long & they'll have a design shortly to run by tools-discuss. (that's the alias the Bugster team is on, so they probably won't even see these notes) Valerie -- Valerie Bubb, http://blogs.sun.com/bubbva Solaris Security Technologies, Developer, Sun Microsystems, Inc. 17 Network Circle, Menlo Park, CA, 94025. 650-786-0461
