I picked up the latest build (M-3.2.1-20100716070539)
and I can't recreate this problem with the instructions provided.We will continue to monitor this bug,
but I vote to promote this build
Thanks - Chuck