[Libreoffice-qa] Stagnant NEEDINFO bugs

[Petr Mladek]

Alex Thurgood píše v Čt 07. 02. 2013 v 14:17 +0100:
> Le 07/02/2013 13:32, Petr Mladek a écrit :
> 
> Hi Petr,
> 
> > I am confused. Are these bugs in NEEDINFO just because nobody found time
> > to confirm them? If this is true, they should be in the state
> > UNCONFIRMED.
> > 
> > The bugs should be in the state NEEDINFO only when they can't be
> > reproduced because an information is missing.
> > 
> > Could you please give an example of such bugs?
> > 
> 
> https://bugs.freedesktop.org/buglist.cgi?order=Importance&emailcc1=1&emailreporter1=1&emaillongdesc1=1&emailtype1=substring&query_format=advanced&emailassigned_to1=1&emailqa_contact1=1&bug_status=NEEDINFO&email1=iplaw67&product=LibreOffice

Hmm, I took random 10 bugs from the above list. I see that Alex did a
lot of great work. Anyway, here is what I see:

+ https://bugs.freedesktop.org/show_bug.cgi?id=52170:
  	+ An extremely slow search/browse table in embedded HSQLDB
	+ in NEEDINFO for a long time but there was a lot of activity
          later
	+ IMHO, it should not be in NEEDINFO
	+ in each case, we should stay opened

+ https://bugs.freedesktop.org/show_bug.cgi?id=52388:
	+ EDITING - postgresql data not writable, updatable, modifiable
          using built-in connector
	+ Lionel (developer) is not able to move forward without more
          info
	+ 2 month in needinfo and no reaction
	+ => should get closed

+ https://bugs.freedesktop.org/show_bug.cgi?id=53862:
	+ EDITING: Inserted graphics are lost
	+ hard to reproduce without test document
	+ potential duplicate of other bugs
	+ 2.5 months in NEEDINFO and no reaction
	+ => should get closed; there are probably better duplicates;
             we do not have resources to create a working test document;
             if it is a common bug, it will be reported later and maybe
             with a test document

+ https://bugs.freedesktop.org/show_bug.cgi?id=51390:
	+ Users with network based accounts on Mac OS X 10.6
	+ bug triages is not able to reproduce because of missing HW
          and complicated setup
	+ asked for backtrace 3 months ago and no response
	+ I would close this; it is trivial to produce back trace
          and it should be enough to fix the problem
	+ NOTE: there is missing a link to the wiki with the hint
          how to create the back trace; Anyway, the user could have
          asked

+ https://bugs.freedesktop.org/show_bug.cgi?id=55753
	+ CRASH - new template manager dialog from StartCenter
	+ information provided
	+ => wrong state and should stay opened

+ https://bugs.freedesktop.org/show_bug.cgi?id=46040
	+ UI: Docking the task window crashes LibreOffice 3.5 Impress
	+ can't be reproduced
	+ 1 year agi asked for more info
	+ 1 month ago pinged and no answer
	+ => should get closed

+ https://bugs.freedesktop.org/show_bug.cgi?id=52571
  	+ BASE VBA DELETE COLUMN OR TABLE DOESN'T CHANGE THE SURFACE
	+ minimalistic report => hard to understand
	+ 5 months ago asked for more details and no answer
	+ 2 months ago pinged 
        => should get closed

+ https://bugs.freedesktop.org/show_bug.cgi?id=55085
  	+ Landscape printing prints as portrait with content turned at
          90 degree
	+ too vague report
	+ 4 months in needinfo and no reaction
	+ => should get closed

+ https://bugs.freedesktop.org/show_bug.cgi?id=54730
	+ LibreOffice Base crashes when Test connection is executed
          against JDBC connection
	+ problems to reproduce
	+ 4 months in needinfo
	+ info kind of provided but still not reproducible
	=> should get closed as worksforme

+ https://bugs.freedesktop.org/show_bug.cgi?id=36970
	+ (orcmid) Help on Managing Digital Signatures is incorrect
	+ not producible
	+ 4 month in needinfo and no answer
        => should get closed
	


So, 8 of 10 bugs should get closed. The remaining 2 bugs are in wrong
state.

I am not sure if this sample is enough but I am even more convinced that

	+ it makes sense to close such bugs because they are mostly dead
	+ ping does not make any sense; if users do not provide the
          info when asked they do not react on ping as well

Note that even if we close few bugs by mistake, it is not that bad. It
makes traffic there and encourages people to move forward.

I still do not understand that many fears and bad feeling about this
action.

Do you have other opinion, feeling, or experience, please?

Best Regards,
Petr