Originally posted by xiando
View Post
That probably explains why you are expecting a fix more quickly than we would expect to deliver it. I'm not saying there is anything wrong with your thinking, but I expect it is different from the way the developers are approaching the problem.
I agree that if a better solution can not be found reasonably quickly then something like what you suggested might be all we can get into 4.18; just don't think it should be the first approach on the list.
Originally posted by xiando
View Post
If you take two comparable problems (the difficulty of the problem is what really affects fix time, and bisectable regressions are generally the easiest to deal with), file comparable bug tickets and respond comparably to the developers, but scream bloody murder about one and quietly sacrifice a goat to the other, on average you will find that fix times are pretty similar.
Comment