incubator-sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Sling Website > Issue Tracker
Date Mon, 07 Sep 2009 14:30:02 GMT
<html>
<head>
    <base href="http://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/1519/1/1/_/styles/combined.css?spaceKey=SLINGxSITE&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
     <h2><a href="http://cwiki.apache.org/confluence/display/SLINGxSITE/Issue+Tracker">Issue
Tracker</a></h2>
     <h4>Page <b>edited</b> by             <a href="http://cwiki.apache.org/confluence/display/~fmeschbe">Felix
Meschberger</a>
    </h4>
     
          <br/>
     <div class="notificationGreySide">
         <p>Apache Sling uses Jira for tracking bug reports and requests for improvements,
new features, and other changes.</p>

<p>The issue tracker is available at <a href="https://issues.apache.org/jira/browse/SLING"
rel="nofollow">https://issues.apache.org/jira/browse/SLING</a> and is readable by
everyone. A Jira account is needed to create new issues and to comment on existing issues.
Use the <a href="https://issues.apache.org/jira/secure/Signup!default.jspa" rel="nofollow">registration
form</a> to request an account if you do not already have one.</p>

<p>See below for guidelines on creating and managing issues.</p>


<h2><a name="IssueTracker-Issuetype"></a>Issue type</h2>

<p>When creating a new issue, select the issue type based as follows:</p>

<table class='confluenceTable'><tbody>
<tr>
<th class='confluenceTh'> Issue type     </th>
<th class='confluenceTh'> Description </th>
</tr>
<tr>
<td class='confluenceTd'>  <b>Bug</b>          </td>
<td class='confluenceTd'>  Bug reports are used for cases where Sling fails not function
as it should (as defined by some documentation). If you are not certain whether the issue
you've found is actually a bug, please ask the <a href="/confluence/display/SLINGxSITE/Project+Information#ProjectInformation-ProjectInformationMailingLists">Sling
mailing lists</a> first for help. </td>
</tr>
<tr>
<td class='confluenceTd'>  <b>New Feature</b>  </td>
<td class='confluenceTd'>  Use a feature request when Sling does not have some functionality
you need. </td>
</tr>
<tr>
<td class='confluenceTd'>  <b>Improvement</b>  </td>
<td class='confluenceTd'>  Use an improvement request to suggest improvements to existing
features. Typical improvement requests are about updating documentation, increasing stability
and performance, simplifying the implementation, or other such changes that make Sling better
without introducing new features or fixing existing bugs. </td>
</tr>
<tr>
<td class='confluenceTd'>  <b>Test</b>         </td>
<td class='confluenceTd'>  Use this type when contributing test cases for existing features.
Normally test cases should be contributed as a part of the original feature request or as
regression tests associated with bug reports, but sometimes you just want to extend test coverage
by introducing new test cases. This issue type is for such cases. </td>
</tr>
<tr>
<td class='confluenceTd'>  <b>Task</b>         </td>
<td class='confluenceTd'>  Used only for issues related to project infrastructure. </td>
</tr>
</tbody></table>


<h2><a name="IssueTracker-Summary"></a>Summary</h2>

<p>The issue summary should be a short and clear statement that indicates the scope
of the issue. You are probably being too verbose if you exceed the length of the text field.
Use the Environment and Description fields to provide more detailed information.</p>


<h2><a name="IssueTracker-Issuepriority"></a>Issue priority</h2>

<p>Issue priority should be set according to the following:</p>

<table class='confluenceTable'><tbody>
<tr>
<th class='confluenceTh'> Issue priority </th>
<th class='confluenceTh'> Description </th>
</tr>
<tr>
<td class='confluenceTd'>  <b>Blocker</b>      </td>
<td class='confluenceTd'>  Legal or other fundamental issue that makes it impossible
to release Jackrabbit code </td>
</tr>
<tr>
<td class='confluenceTd'>  <b>Critical</b>     </td>
<td class='confluenceTd'>  Major loss of functionality that affects many Slingusers
</td>
</tr>
<tr>
<td class='confluenceTd'>  <b>Major</b>        </td>
<td class='confluenceTd'>  Important issue that should be resolved soon </td>
</tr>
<tr>
<td class='confluenceTd'>  <b>Minor</b>        </td>
<td class='confluenceTd'>  Nice to have issues </td>
</tr>
<tr>
<td class='confluenceTd'>  <b>Trivial</b>      </td>
<td class='confluenceTd'>  Trivial changes that can be applied whenever someone has
extra time </td>
</tr>
</tbody></table>



<h2><a name="IssueTracker-IssueStates"></a>Issue States</h2>

<p>Sling issues can transition through a number of states while being processed:</p>

<table class='confluenceTable'><tbody>
<tr>
<th class='confluenceTh'> State </th>
<th class='confluenceTh'> Description </th>
<th class='confluenceTh'> Next States in Workflow </th>
</tr>
<tr>
<td class='confluenceTd'> <b>Open</b> </td>
<td class='confluenceTd'> The issue has just been created </td>
<td class='confluenceTd'> <em>In Pogress</em> </td>
</tr>
<tr>
<td class='confluenceTd'> <b>In Progress</b> </td>
<td class='confluenceTd'> Work has started on the issue </td>
<td class='confluenceTd'> <em>Documentation Required</em>, <em>Testcase
Required</em>, <em>Documentation/Testcase required</em>, <em>Resolved</em>,
<em>Open</em> </td>
</tr>
<tr>
<td class='confluenceTd'> <b>Documentation Required</b> </td>
<td class='confluenceTd'> Implementation work has finished for this issue. To complete
it documentation must be created and/or updated. </td>
<td class='confluenceTd'> <em>Resolved</em> </td>
</tr>
<tr>
<td class='confluenceTd'> <b>Testcase Required</b> </td>
<td class='confluenceTd'> Implementation work has finished for this issue. To complete
it test cases must be created and/or updated. </td>
<td class='confluenceTd'> <em>Resolved</em> </td>
</tr>
<tr>
<td class='confluenceTd'> <b>Documentation/Testcase Required</b> </td>
<td class='confluenceTd'> Implementation work has finished for this issue. To complete
it documentation and test cases must be created and/or updated. </td>
<td class='confluenceTd'> <em>Resolved</em>, <em>Documentation Required</em>,
<em>Testcase Required</em> </td>
</tr>
<tr>
<td class='confluenceTd'> <b>Resolved</b> </td>
<td class='confluenceTd'> The issue has been resolved from the developers point of view.
Documentation and Testcases have been created and updated as required. Issue is ready for
release. </td>
<td class='confluenceTd'> <em>Reopened</em>, <em>Closed</em>
</td>
</tr>
<tr>
<td class='confluenceTd'> <b>Reopened</b> </td>
<td class='confluenceTd'> A resolved issue has been recognized to contain bugs or to
be incomplete and thus has been reopened. </td>
<td class='confluenceTd'> <em>In Progress</em>, <em>Resolved</em>
</td>
</tr>
<tr>
<td class='confluenceTd'> <b>Closed</b> </td>
<td class='confluenceTd'> Work on this issue has finished and it is included in the
release. </td>
<td class='confluenceTd'> &#8211; </td>
</tr>
</tbody></table>

<p>Users generally create issues and provide feedback while work on the issue is in
progress. When the developer thinks the issue has been resolved, he resolves the issue. At
this point, the user may test the resolution and reopen the issue if it has not really be
solved. Otherwise the user may just acknowledge the fix.</p>

<p>Developers transition the issue through the workflow while working on it. When done
with the issue, they mark the issue resolved with the appropriate resolution and ask the reporting
user to confirm.</p>

<p>Issues are closed once the project against which it has been reported has been released.
Issues once closed cannot be opened again. Rather new issues should be created against the
new release to have broken implementations fixed or extended.</p>



<h2><a name="IssueTracker-Patches"></a>Patches</h2>

<p>When reporting a bug, requesting a feature or propose an improvement, it is a good
thing to attach a patch to the issue. This may speed up issue processing and helps you being
recognized as a good community member leading to closer involvement with Sling.</p>
     </div>
     <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href="http://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
       </div>

       <a href="http://cwiki.apache.org/confluence/display/SLINGxSITE/Issue+Tracker">View
Online</a>
       |
       <a href="http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=2853620&revisedVersion=3&originalVersion=2">View
Change</a>
              |
       <a href="http://cwiki.apache.org/confluence/display/SLINGxSITE/Issue+Tracker?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message