Users of 1.2.0 should upgrade to 1.2.1

15/1/2011

Due to an instability in 1.2.0, see the release note. This bug was seen once in beta testing but we weren't able to reproduce. It is now fixed in 1.2.1. We apologise for any inconveniance.