Author: buildbot
Date: Sun Jul 14 10:00:42 2013
New Revision: 869431
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 Sun Jul 14 10:00:42 2013
@@ -1 +1 @@
-1502242
+1502951
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 Sun Jul
14 10:00:42 2013
@@ -85,8 +85,7 @@
<h1 id="project-management-pmc">Project Management PMC</h1>
<ul>
<li><a href="http://blogs.apache.org/OOo/";>Project Blog</a></li>
-<li><a href="/pmc-faqs.html">PMC FAQs</a><br />
-</li>
+<li><a href="/pmc-faqs.html">PMC FAQs</a> </li>
</ul>
<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
<ul>
@@ -105,9 +104,8 @@ about basic tasks that are easiest to do
<p>To complete this module, read through the material on this page, including
the linked references. There will also
be some start-up tasks for you to perform, such as signing up for an account
in our defect tracking database.</p>
<p>Your first task is to subscribe to our QA mailing list and to introduce
yourself to the other QA volunteers. You
-can subscribe by sending an email to <a
href="mailto:[email protected]";>[email protected]</a>.<br
/>
-</p>
-<p>Then you can introduce yourself by <a
href="mailto:[email protected]?subject=New QA Volunteer">sending an
email to the list</a>.
+can subscribe by sending an email to <a
href="mailto:[email protected]";>[email protected]</a>.
</p>
+<p>Then you can introduce yourself by <a
href="mailto:[email protected]?subject=New%20QA%20Volunteer";>sending
an email to the list</a>.
We'd love to hear who you are, where you are from, what your background is,
etc. Also as you work through the
items on this page, if you have questions or problems, please feel free to ask
for help by sending a note to
this same list.</p>
@@ -138,8 +136,7 @@ of improving the Apache OpenOffice produ
<li>As an extremely popular open source product, with many millions of users,
there are opportunities here to do some new and exciting things on the QA
front, including possibilities of crowd sourcing some kinds of testing.</li>
</ul>
<h2 id="qa-activities">QA Activities</h2>
-<p>QA activities within the Apache OpenOffice project include: <br />
-</p>
+<p>QA activities within the Apache OpenOffice project include: </p>
<ul>
<li>Reviewing incoming bug reports from users to see if the reported issues
can be reproduced</li>
<li>Verifying bugs that the developers say they have fixed, to confirm that
they actually have been fixed</li>
@@ -192,10 +189,9 @@ could be major or minor. They could inc
could make your system unstable. So QA volunteers generally try to separate
their QA work from their normal
desktop activities. You don't want to write your thesis on a test build!</p>
<p>Some volunteers simply use two machines: one dedicated to their testing
work. If things become unstable they can
-then reinstall the operating system and start fresh. <br />
-</p>
+then reinstall the operating system and start fresh. </p>
<p>A more sophisticated approach is to use virtual machines,
-which can work quite well. <a href="http://www.virtualbox.org";>VirtualBox</a>
is a popular visualization package.</p>
+which can work quite well. <a href="http://www.virtualbox.org";>VirtualBox</a>
is a popular virtualization package.</p>
<p>Feel free to ask questions on the QA list about effective ways to manage a
test environment.</p>
<p>Once you have your test environment set up, you need to download and
install the latest OpenOffice build. </p>
<ul>
@@ -229,12 +225,10 @@ step, since we'll try to give you easier
<li>First, assign the report to yourself by setting your Bugzilla username
(your email address) in the "QA Contact" field. If you are not able to
add yourself, then send a note to the QA mailing list asking to be added to
the "qa-team" group in Bugzilla.</li>
<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>
+ does not mean that it is a defect report. </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>
+You can now set the Status to CONFIRMED and then save your changes. You are
done with the report. </li>
<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,
@@ -251,7 +245,7 @@ You can now set the Status to CONFIRMED
</li>
</ol>
<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,
+set the "needmoreinfo" 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>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
@@ -294,7 +288,7 @@ writing up defect reports for any new de
<h2 id="module-completion">Module Completion</h2>
<p>Once you have done the above, go to our our <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers";>Directory
of Volunteers</a> wiki page and add or update your
information. Also, add an entry for yourself to the <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/QA+Testing+Preferences";>QA
Testing Preferences</a> page. Congratulations!<br />
-Please send a note to <a
href="mailto:[email protected]?subject=Completed Introduction to
QA">[email protected]</a> so we know.</p>
+Please send a note to <a
href="mailto:[email protected]?subject=Completed%20Introduction%20to%20QA";>[email protected]</a>
so we know.</p>
</div>
<div id="footera">
