Just wondering if anyone can provide a clarification on the status of what we're planning to do with this (?) It seemed that initially there was some urgency around trying to rapidly release a 3.2.1GA to get this modification officially out there for people but then this thread has sat idle for 8+ days now. The issue shows RESOLVED so we should be clear to release a 3.2.1GA at this point AFAIK. Are there other blockers preventing this at this point that need attention or is it possible to proceed with the release now?
(concerned for the performance implications of having this issue present in our latest 'official' release out there for adopters) Thoughts --? -Steve B.
