-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-12-10 14:55, Lars Müller wrote:
On Wed, Dec 10, 2014 at 01:08:42AM +0100, Carlos E. R. 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.
And you've read comment #2?
No, please don't answer to this question. It was a rhetorical one.
But I will: it is not my issue, it is the openSUSE organization issue. I only point out its presence, I don't personally care. And in this case, the issue is not related to a particular distribution, so closing the "bug" because the release number cited in the description is obsolete is incorrect. That's the issue here, not the content of that particular report. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlSJwcUACgkQtTMYHG2NR9X7cACeIQPa0GKpgf3zFyIFLmLaQ7Ed 1hwAoJIqJfzJdT4haaguovVwpcYt/fNN =I4g+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org