From: "Gross, Christopher W. (Chris)" <[email-masked]>
Date: Mon, 16 Sep 2013 11:38:04 +0000

This is very disappointing. It's been 6 months since this report was filed (and since the last release) and even though it was acknowledged in July, it still was not fixed in the current version. Will we be stuck with this bug for another six months?