jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Jackrabbit: Issue Tracker (page created)
Date Wed, 20 Feb 2008 22:58:00 GMT
Issue Tracker (JCR) created by Jukka Zitting
   http://cwiki.apache.org/confluence/display/JCR/Issue+Tracker

Content:
---------------------------------------------------------------------

Apache Jackrabbit uses Jira for tracking bug reports and requests for improvements, new features,
and other changes.

The issue tracker is available at https://issues.apache.org/jira/browse/JCR and is readable
by everyone. A Jira account is needed to create new issues and to comment on existing issues.
Use the [registration form|https://issues.apache.org/jira/secure/Signup!default.jspa] to request
an account if you do not already have one.

See below for guidelines on creating and managing issues.

h2. Issue type

When creating a new issue, select the issue type based as follows:

* *Bug* Bug reports are used for cases where Jackrabbit fails not function as it should (as
defined by the JCR specification or some other documentation). If you are not certain whether
the issue you've found is actually a bug, please ask the Jackrabbit [mailing lists] first
for help.
* *New Feature* A feature requests is used
* *Improvement* 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 Jackrabbit better without
introducing new features or fixing existing bugs.
* *Test* 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.
* *Task* Used for issues related to project infrastructure.

h2. Issue priority

Issue priority should be set according to the following:

* *Blocker* Legal or other fundamental issue that makes it impossible to release Jackrabbit
code
* *Critical* Major loss of functionality that affects many Jackrabbit users
* *Major* Important issue that should be resolved soon
* *Minor* Nice to have issues
* *Trivial* Trivial non-functional changes that could be applied whenever someone has extra
time


---------------------------------------------------------------------
CONFLUENCE INFORMATION
This message is automatically generated by Confluence

Unsubscribe or edit your notifications preferences
   http://cwiki.apache.org/confluence/users/viewnotifications.action

If you think it was sent incorrectly contact one of the administrators
   http://cwiki.apache.org/confluence/administrators.action

If you want more information on Confluence, or have a bug to report see
   http://www.atlassian.com/software/confluence



Mime
View raw message