openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r849798 - in /websites/staging/openoffice/trunk/content: ./ orientation/intro-qa.html
Date Thu, 07 Feb 2013 18:26:43 GMT
Author: buildbot
Date: Thu Feb  7 18:26:43 2013
New Revision: 849798

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    websites/staging/openoffice/trunk/content/orientation/intro-qa.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Feb  7 18:26:43 2013
@@ -1 +1 @@
-1443641
+1443643

Modified: websites/staging/openoffice/trunk/content/orientation/intro-qa.html
==============================================================================
--- websites/staging/openoffice/trunk/content/orientation/intro-qa.html (original)
+++ websites/staging/openoffice/trunk/content/orientation/intro-qa.html Thu Feb  7 18:26:43
2013
@@ -226,23 +226,23 @@ step, since we'll try to give you easier
 <p>Here's what to do to confirm a new defect report:</p>
 <ol>
 <li>First, assign the report to yourself by setting your Bugzilla username (your email
address) in the "QA Contact" field.</li>
-<li>Then read over the report.  What are they really saying?  Are the reporting a bug?
 Asking for a new feature?  Asking a support question?  Just because it is in Bugzilla
+<li>Then read over the report.  What are they really saying?  Are they reporting a
bug?  Asking for a new feature?  Asking a support question?  Just because it is in Bugzilla
  does not mean that it is a defect report.<br />
 </li>
 <li>Ask yourself:  Are they saying that something is working incorrectly?  Or are they
asking for new functionality?
 If they are asking for a new feature, change the Issue Type field to "FEATURE".  If they
are asking for an enhancement of an existing feature, set the Issue Type field to "ENHANCEMENT".
 You can now set the Status to CONFIRMED and then save your changes.  You are done with the
report.<br />
 </li>
-<li>Search Bugzilla to see if this is a duplicate defect report.  If it is, change
the Status to RESOLVED, DUPLICATE and type in the defect number that this report is a duplicate
of.<br />
- You are now done with this report.<ol>
+<li>Otherwise, search Bugzilla for keywords related to the bug report to see if this
is a duplicate defect report.  If it is, change the Status to RESOLVED/DUPLICATE and type
in 
+ the defect number that this report is a duplicate of.  You are now done with this report.<ol>
 <li>If the report is actually reporting a defect, then you have more work to do.  Try
to reproduce it with the latest release of OpenOffice. If you can reproduce the defect, 
  set the Status to CONFIRMED, set the "Last Confirmation" field to the release that you tested
with, and set the Importance field to an appropriate value, depending on the severity 
  of the defect.</li>
-<li>If the report is not clear enough to reproduce, enter a comment asking the user
for more information and add "needmoreinfo" to the Keyword field. Be specific about what information
+<li>If the report is not clear enough to reproduce, enter a comment asking the user
for more information and add the "needmoreinfo" to the Keyword field. Be specific about what
information
  you need:  more detailed steps, a test document, clarification about what version they are
running, etc.  When the user responds you will be copied on 
  their response and can continue with this report.  But for now you are done with this report.</li>
-<li>If you testing cannot reproduce the bug, and you <em>do not</em> need
more information from the user, then change the status to RESOLVED/IRREPRODUCIBLE.</li>
-<li>If the user was confused, did not understand the functionality, was asking a support
question, etc., then point them to the <a href="http://forum.openoffice.org">Community
Support Forums</a>
+<li>If your testing cannot reproduce the bug, and you <strong>do not</strong>
need more information from the user, then change the status to RESOLVED/IRREPRODUCIBLE.</li>
+<li>If the user was confused, did not understand the functionality or was asking a
support question, then point them to the <a href="http://forum.openoffice.org">Community
Support Forums</a>
  and mark the issue as RESOLVED/INVALID.  Of course, you can help if it is a simple question,
but the forums are the better place for a user to find help.  Bugzilla is not for 
  support.  It is for reporting bugs.</li>
 </ol>
@@ -251,10 +251,10 @@ You can now set the Status to CONFIRMED 
 <p>Note: Once you have reviewed a bug report, it should only be left in the UNCONFIRMED
state if you are waiting for more information from the user, in which case you should also
 set the "needsmoreinfo" value into the Keyword field.  In all other cases you should push
the report forward to a new status, either CONFIRMED, RESOLVED/IRREPRODUCIBLE,
 RESOLVED/INVALID or RESOLVED/DUPLICATE, or by changing the Issue Type to FEATURE or ENHANCEMENT.</p>
-<p>Also, it is a judgement call on whether to immediately mark an issue RESOLVED/IRREPRODUCIBLE
or to send the user a question and wait for a response. </p>
-<p>An intermediate approach, when confirming defects report written against older versions
of OpenOffice, is to mark the bug as RESOLVED/IRREPRODUCIBLE and at the same time add a 
-comment saying, "I was not able to confirm the bug given these steps in the current version
of OpenOffice (AOO 3.4.1), so I'm closing this report.  If you are still seeing this 
-problem after upgrading to AOO 3.4.1 please post the details and we can reopen the report".</p>
+<p>It is a judgement call on whether to immediately mark an issue RESOLVED/IRREPRODUCIBLE
or to send the user a question and wait for a response. An intermediate approach, when confirming

+defects report written against older versions of OpenOffice, is to mark the bug as RESOLVED/IRREPRODUCIBLE
and at the same time add a comment saying, "I was not able to confirm the 
+bug given these steps in the current version of OpenOffice (AOO 3.4.1), so I'm closing this
report.  If you are still seeing this problem after upgrading to AOO 3.4.1 please post 
+the details and we can reopen the report".</p>
 <p>Finally, think of the confirmation process as the opportunity for the QA Team to
improve the value of information we receive from users.  We're taking the raw bug reports,
 sorting through them, eliminating the ones that do not report new bugs, and then passing
on the good ones to the programmers.  So anything you can do to improve the quality
 of the incoming defect reports will help.  This includes clarifying the steps needed to reproduce
the problem, attaching sample documents that you might create to reproduce the



Mime
View raw message