Considering 2.0.2 was release _very_ quickly after 2.0, with no information about changes and with a small increase in version number... I'd say it was purely a bug fix found at the last moment. I'm running it without issue.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
