His three bugs of choice were some compilation errors from the source, correction of some icons on Windows, and adding a Reader for Properties.load(). In each case he fixed the bug, and then sent the patches to Sun.
In the issue of the compiler warnings, a Sun engineer responded within four days that the patch had been accepted and should be in the integration build in two weeks (which would place it in the integration stream around the second week of April, 2005).
For the Windows icon issue, an engineer responded that the fix wasn't complete, that another engineer was fine-tuning the process for loading the icon from Windows.
On the Properties.load() change, he had not received an update by the time of his writing the article, which might indicate that it was still under review.
In all three cases, Sun did a good job of communicating: I got an automatically generated form letter immediately after submission of the fix, and a followup email from a real person once they had analyzed the fix. And once a fix had been incorporated, I got a third email telling me so (and letting me know I get a free T-shirt).
And, of course, the good news is that my submitted fixes seemed to find their way to the right person within Sun. That may not sound like a big deal, but it's probably quite an accomplishment for a fairly large company like Sun.His conclusion final conclusion was also positive:
Overall I'd give Sun a 'B+', or '3 stars out of 4', or 'very good' rating.