※このページは翻訳中です。※ How to File a Documentation Bug GlassFish uses Issue Tracker for bugs and RFEs (requests for enhancements). This page describes how to file a GlassFish documenation bug or RFE. Questions about this process as it applies to GlassFish documentation? Contact the [doc team].
\ Before You Begin You must be logged in to java.net to submit an issue. Information about how to get an account if you don't yet have one is provided below.
\ Filing a GlassFish Documentation Bug 1. Go to the GlassFish Community site and click Login. 2. In the Login page, log in with your java.net username or email and password. If you're a new user, follow the link to register for an account to receive a password and log in. 3. After logging in, click Issue Tracker in the list on the left. 4. Query the database to make sure the bug or RFE doesn't already exist. ALWAYS search before reporting an issue to avoid duplication. 5. 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 Enhancement to submit an RFE. 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. 6. On the Enter Issue page, complete the fields:
-
- Found in Version.* Select the product version to which the documentation issue applies.
-
- Subcomponent.* Select docs.
-
- 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 customers; fix is required
- P2 --* Severe problems that affect a significant number of customers; fix is required; rarely if ever used for docs
- P1 --* Severe, show-stopper issues; fix is required immediately; rarely if ever used for docs
-
- 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 bug will automatically be assigned to the subcomponent (docs) owner.
-
- CC.* If desired, enter a space-separated list of glassfish.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. 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 issue per bug report! Do not include several problems in one report. File a separate report 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.
7. When you've completed the form and are ready to submit the issue, click Submit Issue.
\ 日本語翻訳: XXXXX 英文 (翻訳したバージョン: 18)
|
