On Wed, Dec 10, 2014 at 01:08:42AM +0100, Carlos E. R. wrote:
On 2014-12-08 11:32, Bernhard M. Wiedemann wrote:
On 2014-12-08 05:00, Carlos E. R. wrote:
On 2014-12-07 18:21, Bruno Friedmann wrote:
On Sunday 07 December 2014 15.01:02 Carlos E. R. wrote:
Some of these bugs took me days, even weeks, to try collect the data.
Some of these automatically closed bugs are still present on the new releases (sometimes obviously so), so I reopen them. And they often are eventually closed again without activity on the next release.
please give some links, so I can have a look
Let me see if I can locate some samples [...] ok.
For instance, 765084, was bureaucratically closed. I spent many hours of effort on it, even wrote changes to the kernel.
Dude, Jeff made the usual post release cleanup. It had been your opportunity to evaluate this with the 12.2 release. This unfortunately happens quite often and everyone of us has to shift reports from one release to the next.
It is just an example, I do not want that particular one reopened. My memory is not what it was, I simply located that one first.
Date: Fri, 3 Feb 2012 22:12:51 +0000 Subject: [Bug 745024] Kernel vmlinuz-3.1.9-1.4 update failure
was bureaucratically closed on Fri, 8 Aug 2014, a year later. Never really solved, just closed. Of course, it is now impossible and pointless to try to solve.
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.
Or this one, a curious one for the community:
Date: Thu, 17 Nov 2011 04:05:59 +0000 Subject: [Bug 730912] Gramar rules need to be changed for "openSUSE".
This one was about LO forcing grammar rules to write "OpenSUSE" at the start of sentences. Was bureaucratically closed on Mon, 28 Jul 2014, and I reopened it a month later, because the "bug" is of course still present.
And you've read comment #2? No, please don't answer to this question. It was a rhetorical one.
No, I do not intend to pursue the matter upstream myself, I can not convince anybody there. Some heavy weight from Novell/SUSE/openSUSE has to do that. This bugzilla tracks the situation. (I thought that Novell was a big contributor to OOo previously... :-? They should have the force to make this change)
Comment #6 is the usual, I expect some automated post release cleanup Andreas did. And the value of comment #7 is close to 0 in the light of comment #2. Sorry, it's not this easy to blame others. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany