FW: [PROPOSAL] On Reproducibility of Defects

["Dennis E. Hamilton" <or...@apache.org>]

Here's another.  It is so easy to just keep responding on a thread where something first comes up.  I will do better on this.

 - Dennis

-----Original Message-----
From: Dennis E. Hamilton [mailto:orcmid@apache.org] 
Sent: Thursday, September 17, 2015 19:17
To: qa@openoffice.apache.org; orcmid@apache.org
Subject: RE: [PROPOSAL] On Reproducibility of Defects

Update at the end ...

-----Original Message-----
From: Dennis E. Hamilton [mailto:orcmid@apache.org] 
Sent: Thursday, September 17, 2015 14:22
To: qa@openoffice.apache.org
Subject: [PROPOSAL] On Reproducibility of Defects

I have a suggestion with regard to reproducibility of reported defects.

First, it is important to reproduce using the same release and platform as the reporter if at all possible.  

If the user has a configuration that is not available for confirming yet the bug can't be reproduced with the current released version on the same platform, that should be reported so that others can take a look.  Also, the reporter should have the opportunity to see if they can deepen the information about their case.

If the incident can't be reproduced with a development build, be certain that it can be reproduced with the current release on the same platform.  If not, treat that as if it is the previous case.  

If it is a defect that is confirmed for the current release and not reproducible for an in-development release, please confirm the defect and set the target for fix to the coming version.  If there is a workaround until an update is released, provide that.

 - Dennis

PS: I have no thoughts on when such an issue should be marked resolved.  I would recommend waiting until the next release has a release candidate, at the earliest, and there is a final check.  (These are good regression checkers.)

<orcmid>
  Duhh.  The obvious time to mark it resolved is when the reporter(s) confirms that the problem does not occur with a new release.  
</orcmid>

PPS: It is easy for users to see similarities in their own experience and add their report as a comment to a current issue.  The only way I know to determine that is to ask for more detail and if there is indication of a clear difference, create a new issue and lead the user to it.



---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org