RE: How best to get Oracle to divulge "proprietary information"
- From: "Powell, Mark D" <mark.powell@xxxxxxx>
- To: "oracle-l" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 3 Oct 2006 15:19:43 -0400
I agree. Every bug should have a public description that provides an
explanation of the bug symptoms, where possible provides code to
reproduce the bug, lists workarounds where any exits, lists the versions
affected, and lists the patch numbers or expected future patch levels
where the fix will be included.
-- Mark D Powell --
Phone (313) 592-5148
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jacques Kilchoer
Sent: Tuesday, October 03, 2006 2:59 PM
To: oracle-l
Subject: RE: How best to get Oracle to divulge "proprietary information"
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.
...
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
