| | 47 | |
| | 48 | === Milestones and Versions === |
| | 49 | |
| | 50 | When entering tickets, you will be asked to provide a version and a |
| | 51 | milestone. |
| | 52 | |
| | 53 | The [http://trac.edgewall.org/wiki/TracTickets TRAC documentation] defines |
| | 54 | these terms as |
| | 55 | |
| | 56 | * Version - Version of the project that this ticket pertains to. |
| | 57 | * Milestone - When this issue should be resolved at the latest. |
| | 58 | |
| | 59 | For new tickets, the version will default to current ACPI version (i.e. |
| | 60 | 3.09). |
| | 61 | If you are reporting for some other version, please override the default. |
| | 62 | If you are opening the ticket for testcase release, please note the testcase |
| | 63 | version in the ticket summmary. |
| | 64 | |
| | 65 | The milestone will default to the next scheduled ACPI version release (i.e. |
| | 66 | 3.10). |
| | 67 | |
| | 68 | Genernally, once a ticket is opened, the version should not be changed. If |
| | 69 | the issue is not resolved, the milestone will be changed to reflect when the |
| | 70 | ticket is expected to be resolved. |
| | 71 | |
| | 72 | Tickets will be closed as resolved when the reported issue is fully |
| | 73 | resolved. |
| | 74 | A ticket is considered resolved when the reporter states that the |
| | 75 | issue no longer occurs. |
| | 76 | |
| | 77 | If a ticket can not be not resolved for the current version, the ticket will |
| | 78 | left open and the milestone will changed. |
| | 79 | |
| | 80 | When an issue is corrected by code changes, it is recommended that ticket is |
| | 81 | updated to show the Subversion changeset number. |
| | 82 | |
| | 83 | |