Leif, First, I may be inconsequential, but I did not see any apology. Perhaps it only went out on the dev list..... Second, I am not concerned about receiving multiple iterations of the bug closing, but as you suggest, by the closing of a bug simply because it was too much trouble to address. Third, the bug in question in my case was not only clearly identified, but a solution proposed months ago. Fourth, the bug was reclassified in March because the bug tracker was redone, requiring me to reconfirm Fifth, then a few weeks later (end of March 2012) I was asked again to reconfirm and I did.
While I agree that whining here is not the answer, I am at a loss as to what else we can do other than to identify the bug, identify the code needed, and identify the source of the needed code. I understand that my little issue is NOT a show stopper, but I am horrified just thinking about what other bugs were simply marked "resolved" that may be the result of even more effort than we put in on the little item I was involved with. I have had my little rant, for what it is worth, and I hope that there are some devs on this list that may take the message to heart, and that is that. Apologies to all. On 8/14/12 12:32 PM, leif wrote: > Hello Marc, > > I feel the same as you. some of these bugs are not closed because they > "need info" but because we need developers. We can't do much about that, > but we should not behave like this to our polite bug reporters. This is > not a serious way to embrace community members. > > I can understand that the developers and QA team needs a better overview > of bugs - but this is not the best way to deal with the problem. Perhaps > better communication or something else could help, but not this > approach, please. > > > Cheers, > Leif Lodahl > > Cheers, > Leif Lodahl > > > On 14-08-2012 20:48, Marc Grober wrote: >> This (see the quote below) is simply unacceptable. In fact, with respect >> to the bug on which I received this little gem quite a few people had >> been at pains to clearly identify the problem and the potential >> solution, and neither having changed at all, there had been no changes >> to the bug report save angry responses everytime someone tried to close >> it because it had not been updated. What is Florian really saying? It >> would appear to be either that the product is SOOOOO buggy we have >> decided to ignore all the bug reports OR that users are SOOOO stupid >> that we are going to ignore all bug reports.... Thank you, Florian, for >> the vote of confidence. >> >> If I had the time I would go through and re-open every one of these >> simply to give Florian something to do. >> >>> Dear bug submitter! >>> Due to the fact, that there are a lot of NEEDINFO bugs with no answer >>> within >>> the last six months, we close all of these bugs. >>> To keep this message short, more infos are available @ >>> https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement >>> Thanks for understanding and hopefully updating your bug, so that >>> everything is >>> prepared for developers to fix your problem. >>> Yours! >>> Florian >> > > -- For unsubscribe instructions e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
