Guidelines
- Please do a quick search of the bug database to see if your issue has already been filed
- You must include a test case, or clearly enumerated steps to setup and reproduce the failure
- We can't fix a problem we can't reproduce
- Set the Components field and labels so the bugs can be routed to the right engineers
- If there are any crash logs, spin traces, or gdb stack output, please also attach them to the bug
- If you are reporting a graphical UI issue, screen shots are very helpful
- Include any version information about the build, as well as the version of Mac OS X you encountered the problem on
- Use the form below if you are new to filing bugs or are uncertain of what information to attach
...
Priorities
Blocker: Blocks development and/ or testing work, production could can not run.
Critical: Crashes, loss of data, severe memory leak. Major specification
incompatibility.leaks, major specification incompatibility
Major: Major loss of function. Minor functionality, minor specification incompatibility.
Major , major behavioral incompatibility.
Minor: Minor loss of function. Minor functionality, minor behavioral incompatibility.
Trivial: Cosmetic problem problems like misspelt misspelled words or misalignes misaligned text.
Tags
- REGR_from_apple6: bug test cases passes on Apple's Java SE 6, fails on macosx-port
- not_REGR_from_apple6: bug test case also fails on Apple's Java SE 6
Where to file
Apple Bug Report Sample Form
This form may be a helpful template if you are new to filing bugs
...