Here's another way to look at it.
Date/time:
on v.1.8.0.467 jv16PT.exe: Thursday, August 14, 2008, 1725 (GMT+2) or 0925 (GMT-6) (release estimate)
of first member bug report: Thursday, August 14, 2008, 1103 (1 hour, 38 minutes after release)
of first jv16 request for more information: Friday, August 15, 2008 0029 (15 hours, 4 minutes after release)
of last member bug report: Friday, August 15, 2008, 1013 (24 hours, 48 minutes after release)
of last member fix analysis report: Sunday, August 17, 2008, 0521 (67 hours, 56 minutes after release)
of first jv16 fix post: Monday, August 18, 2008 0235 (89 hours, 10 minutes after release)
of most recent jv16 fix post (6th of 6): Monday, August 18, 2008 1057 (97 hours, 32 minutes after release)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Note: All times are GMT-06, except possibly the executable's time which may be GMT+02.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
jv16 must have put in some time over the weekend. :
His six fix posts cover nine lines in the issue list (I think …).
I speculate that by the next release time, he will have addressed 2 to 5 more issues (the "empty FileCache.dat" at a minimum).
