|
Project Darkstar uses the java.net Issue Tracker for bugs and RFEs (requests for enhancements). This page describes how to use Issue Tracker to file a Project Darkstar Issue. A. Before You Begin - You must be logged in to java.net to submit an issue for Project Darkstar. Follow these instructions to register with java.net
- The Project Darkstar Server consists of two components and each has its own Issue Tracker:
- New components (with separate Issue Trackers) may be added to this list over time.
- It is expected that the majority of Project Darkstar issues encountered will be relevant to the server distribution, but please file your issue in the Issue Tracker of the component where you encountered the issue.
B. Filing a Project Darkstar Bug or Request for Enhancement - Go to the appropriate Issue Tracker (links above) and Login with your java.net user name and password. If you're a new user, follow the link to register for an account to receive a password and log in.
- Query the database to make sure the issue doesn't already exist. ALWAYS search before reporting an issue to avoid duplication.
- If the issue has not been reported, click New on the query page (if that's where you still are) or from the main page click Defect to file a bug, or click on Feature for new feature requests, or click on Enhancement for a request for an enhancement to an existing feature. If you don't see the option to add new bugs or RFEs, you're not logged in to java.net. You must be logged in to submit an issue.
- On the Enter Issue page, complete the fields:
- Found in Version. Select the Project Darkstar version to which the issue applies.
- Subcomponent. Select the appropriate subcomponent
- Platform. Select the platform you were using when the problem occurred. If the issue applies to all platforms, select All (the default).
- OS. Select the operating system you were using when the problem occurred. If the issue applies to all operating systems, select All (the default).
- Priority. Indicate the urgency and severity of the issue. P1 indicates the greatest impact, P5 the least. This field defaults to P3. If in doubt, leave it set to P3. In very general terms, the meaning of each ranking is as follows:
- P5 -- Non-critical problems that rarely affect anyone; fix is nice-to-have but not required
- P4 -- Non-critical or rarely occurring problems; fix is strongly desired but not required
- P3 -- Non-trivial problems that most likely affect a noticeable number of developers; fix is required
- P2 -- Severe problems that affect a significant number of developers; fix is required
- P1 -- Severe, show-stopper issues; fix is required immediately
- Issue Type. Make sure the correct issue type is listed (DEFECT for bugs, ENHANCEMENT for RFEs).
Assigned To. Unless you know who the issue should be assigned to, leave this field blank. The issue will be assigned by the core team.
CC. If desired, enter a space-separated list of java.net login names you want to be notified about any subsequent changes to the issue. You as the reporter will be notified automatically, so there's no need to add yourself. Unfortunately, arbitrary email addresses are not accepted by the system.
URL. If applicable, provide a URL that's relevant to the issue and will be helpful to whoever's looking at it.
Summary. Provide a brief (one sentence) description that makes it easy to recognize the issue, easy to find the issue (to check for duplicates), and easy to assess the issue's importance. A meaningful summary is very important. Remember: One problem per issue! Please do not include several problems in one report. File a separate issue for each.
Description. Provide a detailed description that makes it easy for a person looking at the issue for the first time to understand what the issue is, where it occurs, and what needs to happen. Include all relevant information in the description. A complete description is very important. - When you've completed the form and are ready to submit the issue, click Submit Issue.
C. See Also
|
