Support records
Support is recorded per machine and per feature, rather than inferred from a chip generation. A successful result on one Mac does not automatically apply to another Mac with the same chip.
What a support record needs
Section titled “What a support record needs”| Detail | Why it matters |
|---|---|
| Exact Mac model and device ID | Identifies the board and device configuration tested. |
| Operating system and software revision | Makes the result traceable to a particular build. |
| Feature tested | Separates boot, display, input, storage, and networking results. |
| Test method and logs | Helps another contributor reproduce the observation. |
| Limitations | Records partial behavior and known failures. |
Reading a result
Section titled “Reading a result”- Working: The reported feature worked in the recorded test, within its documented limits.
- Partial: Some behavior worked, but there are recorded restrictions or failures.
- Not working: The feature was tested and failed in the recorded conditions.
- Untested: There is no recorded test. This means unknown.
The device page groups features by the hardware in each Mac. Its current support snapshot uses Working, Partial, Not working, and Not recorded. Where only an earlier development report is available, it shows Reported.
Open a feature pill for any restrictions and earlier dated reports. Historical results describe their named software revisions and may differ from the current status.
Reporting a test
Section titled “Reporting a test”Follow the relevant repository’s issue template. Include the exact device, revision, steps, expected result, actual result, and logs. Clearly separate observed behavior from assumptions.
Read the contributor guide and project policies before sharing a report.