Quote:
|
Originally Posted by tony_sologubov
Steve, what you are suggesting is right. I agree that this is not working properly at the moment.
The real problem is we cannot change this right now, because 5.2.2 is designed to be upgraded from 5.1.11 and we cannot ship 5.1.12 that fixes the problem.
I am sorry that this problem is here at the moment.
However, the problem will be fixed in 5.2.x branch and next major upgrade will work smoothly.
Tony
|
I don't think we expect a fix for 5.1.x but I definitely hope that we don't face similar issues after 5.2.x, be best to note it down in a todo list!