Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


I'm forwarding the appended from Florian :-)

        It's clearly good to close the old / obsolete bugs.

        I wonder though - what metric was used; I saw us close some that might
have been in NEEDINFO state for ages, but had active comments recently.
Is it possible to filter those out in future ?

        Anyhow - thanks for all your bugzilla work,

        Regards,

                Michael.

[snip]
Dear developers / contributors of LibreOffice!

Todays cleanup of bugzilla went quite wrong. The same type of message 
got sent to a lot of you (either as reporter or CC) to you.

I really beg your pardon.

For your underatanding: I prepared to send one (1) message, but due to a 
browser, which hang itself up several times, you got 1-4 messages per 
bug. I am really very sorry for that and I hope you didn't uncced any of 
these bugs.

For more info, please write me a PM

PS: the original mail was not sent to a dev-ML would someone please 
forward it - thanks..

Yours

Florian

PS2: I attached 899 bugs, 99% would not be helpful of them and I am in 
CC of every single of them. So please don't write at me if you get too 
many mails. IMHO this was not a one-timer, but next time there will only 
be <50 bugs to change. I hope you understand why this was basically 
necessary...
[/snip]
-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.