I was about to add that the announcement ought to emphasize that is only
reported seen on windows, and other OS'es are not known to be affected,
but Bryan beat me to it...
Good initiative on the 10.3 update release IMHO. Thanks for volunteering
Andrew!
Thomas
Bryan Pendleton wrote:
For what it's worth, I've been running 10.3 in production for 6 months
and have not (to my knowledge) hit this problem. Of course, I run
Linux, which may not have had this problem, but still, I think it's
worth noting that 10.3 has overall been a very good release for me at
least.
thanks,
bryan
P.S. Andrew, thanks very much for volunteering to produce another 10.3
release, I think this will be greatly appreciated by the community.