I am not planning on working on this other than participating in the discussion. My take on this issue is that it is a serious issue that affects both 10.2 and 10.3. Personally I would not hold up 10.3 release waiting on the fix unless someone actively is working on it.
Myrna van Lunteren wrote:
To jump in...Mike, are you intending to fix this? In the foreseeable future?(If you are, then maybe it *is* worth holding the release waiting for it). Myrna
