🚀 go-pugleaf

On Mon, 10 Mar 2003 11:46:12 -0600, Alex Waller wrote:

> Thanks for the advice. I've no experience with submitting 
> "demo code" so this is a good thing to keep in mind. I just
> quickly tapped out the problem via JBuilder and just basically
> "cut and pasted" my code (with a couple of edits ... like the
> copyright statement). 

I'm afraid my comments do not always come across the way I want them 
to.  Just to be clear, you posted a runnable example of the problem, 
which in itself makes it better than the vast majority of the problem 
reports that I see.  I guess it is my nature: whenever I see very good, 
I look toward making it perfect.  :o)

> As for submitting as a bug report. I replied to a previous post
> about that but yeah I used the link near the bottom of the Bug
> Parade page that says "submit a bug!". No luck on three tries.

At times, Sun has been very quick processing bug reports and at other 
times they have been awful.  

In the worst case I ever saw, I submitted a report and forgot about it.  
Over two years later I got an email message saying that some reports 
had gotten waylaid and they wanted to know if I thought it was still 
relevant.

The best time I ever saw was once when I submitted a bug against an RC 
version of the JDK just before the FCS release, and it was processed in 
just a few days.  I imagine they review all bugs submitted against 
release candidates before they give the go-ahead for the release.

If the bug report does not show up on the Bug Parade, you probably 
should just give it time.  Submitting a duplicate will not help, and it 
will just slow Sun down.

-- 
Regards,

John McGrath [TeamB]

---------------------------------------------------
Before sending me e-mail, please read:
    http://www.JPMcGrath.net/newsgroups/e-mail.html