On 13/02/2009, at 5:19 AM, James Cornell wrote:

> Darren Kenny wrote:
>> Hakim,
>>
>> There are several reasons for a bug to disappear off  
>> bugs.opensolaris.org -
>> usually because it contains some "restricted" content - it's  
>> possible that this
>> happened unintentionally, since it's not really clear *what*  
>> exactly can cause
>> some bugs to vanish in this way...
>>
>> Do you have the bug ids? If so one of us that works in Sun might be  
>> able to
>> check it out...
>>
>> As a suggestion, most people are using defect.opensolaris.org as  
>> the open bug
>> tracking system, this is really the best point of call for a non- 
>> Sun user to log
>> their bugs. It may happen that the bug eventually gets transferred  
>> internally,
>> but at least you can still update it and the information should get  
>> to the
>> appropriate developer.
>>
> This is just negligent and is concrete proof that Sun buries  
> anything it
> touches and has not really became as transparent as their media  
> spinners
> want you to think.  Quite pathetic, there's little legal risk with  
> most
> the disappearing bugs, and internal members all the same as external
> should be able to use the same interface regardless.  Who gets to
> comment and change status is up to the developer handling the bug
> report, just how many open-source projects employ Trac for that
> purpose.  Though Sun has a history of making their employees use  
> crappy
> tools to do their work, so go figure.

You know that's not the case. There are a lot of complicated issues  
which are being worked through that have been discussed time and time  
again across the various mailing lists. We can't expose all of the bug  
database overnight because it would expose sensitive information from  
Sun's customer base. We do the best we can while work is in progress  
to improve the situation, and occasionally hiccups happen.

This is why, in part, many of us are using http:// 
defect.opensolaris.org as a way of tracking the bug list in OpenSolaris.


Glynn

Reply via email to