Forums
(@rslindell)
12 years, 6 months ago
Per @semfreak My understanding is that we need to wait for 1.0.3 to be available, which should have addressed this issue.
