Guys, this bug was in "Fix Committed" state for 4.1. We released the 4.1 and now this bug's milestone got changed to 5.0. This is not the way to go, as we want to have a reliable way to query "the list of bugs fixed in 4.1".
As Dmitry said, let's track the new problem under a new bug. This one should be changed back to 4.1, as the original root cause has been fixed in 4.1.
Guys, this bug was in "Fix Committed" state for 4.1. We released the 4.1 and now this bug's milestone got changed to 5.0. This is not the way to go, as we want to have a reliable way to query "the list of bugs fixed in 4.1".
As Dmitry said, let's track the new problem under a new bug. This one should be changed back to 4.1, as the original root cause has been fixed in 4.1.