> > We had this this morning: 2.0 is still getting a good number of bug fixes so if you're going to use it you should be prepared to upgrade to the latest and see if the problem is already fixed before reporting a possible bug.
I have been, but I've seen no similar reports and it may still be in 2.0.6. I will update to that version during a planned maintenance window tomorrow.
