content/qa/ooQAReloaded/Docs/QA-Reloaded-IssueHandlingOverview.html - openoffice-org - Git at Google

 <html lang="en">

     <head>

         <title>About Issues - A Brief Guide</title>
         <style type="text/css"> /* <![CDATA[ */
         <!--
             @import "/branding/css/tigris.css";
             @import "/branding/css/inst.css";
         -->
         /* ]]> */ </style>

     </head>

     <body>

         <div align="right"><font size="-1" color=#BDBEBD>Document written by: <a href="mailto:Joerg.Skottke.Sun.com?subject=OOo QA Project">Joerg Skottke</a></font></div>

         <div class="dba">
             <h1><font size=6 color=#00009C>About Issues - A Brief Guide</font></h1>
         </div>
         <p>This page gives you a brief introduction to how issues are handled
         winthin the OpenOffice.org Quality Assurance. Basically it describes
         an issue's lifecycle and provides direct links to useful documentation.</p>

         <p>You probably came to this page because you have a problem with OpenOffice.org.
         Maybe the application crashed, misbehaved or something else just feels wrong to you.
         So chances are that you found an issue/bug that should be fixed. When you are new to
         writing issues this page should help you to understand the way an issue takes from
         being found to finally being fixed.</p>

         <table border="0">
             <colgroup>
                 <col width="350px" span="1">
                 <col>
             </colgroup>
             <tr>

                 <td><img src="./issue_handling.png" alt="Issue handling flowchart"</td>
                 <td>
                     <ol>
                         <li>It is recommended that you start by
                             <a href="http://www.openoffice.org/servlets/Login">logging in</a>
                             to
                             <a href="http://qa.openoffice.org/servlets/ProjectIssues">IssueTracker</a>.
                             <br>If you want to learn about the benefits of IssueTracker please read
                             <a href="http://qa.openoffice.org/issue_handling/project_issues.html#using">this abstract</a></li>
                             <br><br><br>

                         <li>Please search the IssueTracker database to make sure that your issue does not exist yet.
                             <br>Do a quick search for
                             <a href="http://qa.openoffice.org/issue_handling/pre_submission.html#duplicates">duplicates</a>
                             or go to the more advanced
                             <a href="http://qa.openoffice.org/issues/query.cgi">search form</a>
                             <br>If your issue exists you might want to bookmark it or set yourself on CC</li>
                             <br><br><br>

                         <li>You did not find your issue in the database?
                             <br>Good, go ahead and write a new one using the
                             <a href="http://qa.openoffice.org/issue_handling/submission_gateway.html">submit form</a>.
                             <br>If you are unfamiliar with writing good Bugreports we recommend that you read
                             <a href="http://qa.openoffice.org/issue_handling/basic_rules.html">this document</a>.
                             Following these rules really makes life easier for all.
                             If you want to dig a little deeper you might want to read these detailed
                             <a href="http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html">bug writing guidelines</a>
                             as well.</li>
                             <br><br><br>

                         <li>The issue needs to be confirmed
                             <br>When you are new to OpenOffice.org you don't have the permission to confirm
                             your issues yourself. So somebody with the required permissions will take over at this point.
                             The OOo volunteer will try to reproduce your problem and - in case
                             of failure - get back to you and ask some more questions. If reproduction succeeds
                             the issue gets a target and will be handed over to development for fixing. If the
                             issue can not be reproduced it is closed.</li>
                             <br><br><br>

                         <li>Your issue is added to a
                             <a href="http://wiki.services.openoffice.org/wiki/CWS">CWS</a>
                             (<u>C</u>hild<u>w</u>ork<u>s</u>pace).
                             <br>A childworkspace is created in which your issue is fixed by
                             a developer. When the fix is done the CWS is sent to QA.</li>
                             <br><br><br>

                         <li>The issue needs to be verified on the
                             <a href="http://wiki.services.openoffice.org/wiki/CWS">CWS</a>
                             <br>Your issue will now be verified, meaning that somebody (which could be you as well)
                             takes a look at it by installing a developer build from the CWS.
                             <br>If the fix is not good
                             (failed completely or insufficient) it goes back to development.</li>
                             <br><br><br>

                         <li>The fix is good and gets
                             <a href="http://wiki.services.openoffice.org/wiki/Integration">integrated</a>
                             into the
                             <a href="http://wiki.services.openoffice.org/wiki/MWS">MWS</a>
                             <br>The issue now has the status fixed/verified and gets integrated into the main
                             development line and you can download it with the next developer snapshot.</li>
                             <br><br><br>

                         <li>Final verification of the fix
                             <br>Again somebody verifies that the
                             fix did not by accident get lost or corrupted. If all went well the status is changed to
                             closed/fixed. On any problem the task gets back to development and the cycle starts anew.</li>
                     </ol>

                     <br><br>

                     <p><b><i>Additional hint(s)</i></b></p>

                     <p>When working with issues you always have the possibility to find out where
                     in the process your task is currently located. You just have to look at the status
                     of your issue. If you want to know more about issue states, please take a look at the
                     <a href="http://qa.openoffice.org/nonav/scdocs/issue_lifecycle.html">issue lifecycle</a>
                     document which explains issue states and how they fit into the process in great detail.</p>
                 </td>
             </tr>
         </table>

         <p>Autor: Joerg Skottke (Joerg.Skottke@oracle.com) March 28. 2007</p>
         <p><i>Please do not change this site without acknowledge of the autor or the OOo QA Project Lead/Co-Leads.</i></p>

     </body>

 </html>
	<html lang="en">

	<head>

	<title>About Issues - A Brief Guide</title>
	<style type="text/css"> /* <![CDATA[ */
	<!--
	@import "/branding/css/tigris.css";
	@import "/branding/css/inst.css";
	-->
	/* ]]> */ </style>

	</head>

	<body>

	<div align="right"><font size="-1" color=#BDBEBD>Document written by: <a href="mailto:Joerg.Skottke.Sun.com?subject=OOo QA Project">Joerg Skottke</a></font></div>

	<div class="dba">
	<h1><font size=6 color=#00009C>About Issues - A Brief Guide</font></h1>
	</div>
	<p>This page gives you a brief introduction to how issues are handled
	winthin the OpenOffice.org Quality Assurance. Basically it describes
	an issue's lifecycle and provides direct links to useful documentation.</p>

	<p>You probably came to this page because you have a problem with OpenOffice.org.
	Maybe the application crashed, misbehaved or something else just feels wrong to you.
	So chances are that you found an issue/bug that should be fixed. When you are new to
	writing issues this page should help you to understand the way an issue takes from
	being found to finally being fixed.</p>

	<table border="0">
	<colgroup>
	<col width="350px" span="1">
	<col>
	</colgroup>
	<tr>

	<td><img src="./issue_handling.png" alt="Issue handling flowchart"</td>
	<td>
	<ol>
	<li>It is recommended that you start by
	<a href="http://www.openoffice.org/servlets/Login">logging in</a>
	to
	<a href="http://qa.openoffice.org/servlets/ProjectIssues">IssueTracker</a>.
	<br>If you want to learn about the benefits of IssueTracker please read
	<a href="http://qa.openoffice.org/issue_handling/project_issues.html#using">this abstract</a></li>
	<br><br><br>

	<li>Please search the IssueTracker database to make sure that your issue does not exist yet.
	<br>Do a quick search for
	<a href="http://qa.openoffice.org/issue_handling/pre_submission.html#duplicates">duplicates</a>
	or go to the more advanced
	<a href="http://qa.openoffice.org/issues/query.cgi">search form</a>
	<br>If your issue exists you might want to bookmark it or set yourself on CC</li>
	<br><br><br>

	<li>You did not find your issue in the database?
	<br>Good, go ahead and write a new one using the
	<a href="http://qa.openoffice.org/issue_handling/submission_gateway.html">submit form</a>.
	<br>If you are unfamiliar with writing good Bugreports we recommend that you read
	<a href="http://qa.openoffice.org/issue_handling/basic_rules.html">this document</a>.
	Following these rules really makes life easier for all.
	If you want to dig a little deeper you might want to read these detailed
	<a href="http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html">bug writing guidelines</a>
	as well.</li>
	<br><br><br>

	<li>The issue needs to be confirmed
	<br>When you are new to OpenOffice.org you don't have the permission to confirm
	your issues yourself. So somebody with the required permissions will take over at this point.
	The OOo volunteer will try to reproduce your problem and - in case
	of failure - get back to you and ask some more questions. If reproduction succeeds
	the issue gets a target and will be handed over to development for fixing. If the
	issue can not be reproduced it is closed.</li>
	<br><br><br>

	<li>Your issue is added to a
	<a href="http://wiki.services.openoffice.org/wiki/CWS">CWS</a>
	(<u>C</u>hild<u>w</u>ork<u>s</u>pace).
	<br>A childworkspace is created in which your issue is fixed by
	a developer. When the fix is done the CWS is sent to QA.</li>
	<br><br><br>

	<li>The issue needs to be verified on the
	<a href="http://wiki.services.openoffice.org/wiki/CWS">CWS</a>
	<br>Your issue will now be verified, meaning that somebody (which could be you as well)
	takes a look at it by installing a developer build from the CWS.
	<br>If the fix is not good
	(failed completely or insufficient) it goes back to development.</li>
	<br><br><br>

	<li>The fix is good and gets
	<a href="http://wiki.services.openoffice.org/wiki/Integration">integrated</a>
	into the
	<a href="http://wiki.services.openoffice.org/wiki/MWS">MWS</a>
	<br>The issue now has the status fixed/verified and gets integrated into the main
	development line and you can download it with the next developer snapshot.</li>
	<br><br><br>

	<li>Final verification of the fix
	<br>Again somebody verifies that the
	fix did not by accident get lost or corrupted. If all went well the status is changed to
	closed/fixed. On any problem the task gets back to development and the cycle starts anew.</li>
	</ol>

	<br><br>

	<p><b><i>Additional hint(s)</i></b></p>

	<p>When working with issues you always have the possibility to find out where
	in the process your task is currently located. You just have to look at the status
	of your issue. If you want to know more about issue states, please take a look at the
	<a href="http://qa.openoffice.org/nonav/scdocs/issue_lifecycle.html">issue lifecycle</a>
	document which explains issue states and how they fit into the process in great detail.</p>
	</td>
	</tr>
	</table>

	<p>Autor: Joerg Skottke (Joerg.Skottke@oracle.com) March 28. 2007</p>
	<p><i>Please do not change this site without acknowledge of the autor or the OOo QA Project Lead/Co-Leads.</i></p>

	</body>

	</html>