Hi Dave,

As this was a non-breaking issue for 6.3.x, our procedures automatically schedule it to the next available version, 6.4 in this case and it has now been fixed there. The answer to your question would therefore be no, as it didn't qualify according to these procedures.

Palli

Hi Dave,

I'm sorry about that. As the issue has already been fixed in 6.4.0P3, and the oldest version I have got to verfy is 6.3.11 we probably have to go by the issue description this time.

Palli