Comment 26 for bug 401003

(In reply to comment #13)
> I do not think it is possible to backport the fix to 3.5 without
> knowing just what the fix is, i.e. the commit id(s).

Correct. That’s the problem ...

Therefore, and because our current development focus is 3.6 (and 3.7), while we don’t have infinite developer resources, I fear we have to live with this bug in the 3.5 branch, and just need to encourage people to move on to 3.6.x. (At the moment some people hesitate to update, because there are still some unsolved regressions in 3.6.x, but there is good progress about fixing these regressions, and in my personal experience 3.6.2.1 already works better in most situations than any 3.3.x, 3.4.x or 3.5.x version.)

So, RESOLVED/WORKSFORME is not perfect, but realistic.