I'm with Tim and co on this, I don't think that you can have a blanket publication of all bugs - for privacy reasons, because bad bug descriptions can mislead and for perfectly good IP reasons. What does annoy me is that non-published bugs get linked to in published documents, or returned in metalink searches. You probably can't do anyting about the former, but the latter is embarrasing for a database company IMO. Then of course there is the fact that the free text search doesn't return results when it should.
I think it would be reasonable for Oracle to publish bug descriptions for every bug, removing customer information.
-----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] ...
The problem is customer privacy. There are customer company names, people names, phone numbers, email addresses (i.e. contact info) as well as details about what the customer is trying to do in those bug texts.
-- Niall Litchfield Oracle DBA http://www.orawin.info