On Thu, Dec 11, 2014 at 1:09 PM, Carlos E. R. <carlos.e.r@opensuse.org> wrote:
Again, this isn't "bureaucratically". It's the normal workflow.
All you had to do is to test it with 12.2 and add update the report if it's fixed or if it still exists.
No, that is not the issue. The issue is that, after the reporter spending time and effort on reporting, nothing is done for months or years, then the bug report is removed in the spring cleanup, because it is old. Ok, because that release is no longer supported. That's the point, that nobody did anything on it for many months.
The point is not that the reporter can check whether the issue is still present on the next release.
I've been on both sides of this. As a bug reporter, I want the issue addressed, and silence is very annoying. After long silences, a post merely asking to confirm whether the issue still exists (as if it were to vanish spontaneously for no reason) is also extremely annoying. But as a developer, I know bugs do vanish, seemingly unrelated changes sometimes fix issues, and when someone points out a bug in an old version I immediately search my memory for seemingly related commits that might affect the bug, and end up asking to reproduce the issue on the latest version. As a developer, that saves us lots of blind searching, which is also particularly annoying and exhausting. They key is balance... not asking for it when you can test yourself, not getting annoyed when asked to reproduce something and just do it unless it's very difficult, etc. Sometimes it's good to know both sides. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org