| 121 | = Support and Submitting Tickets = |
| 122 | |
| 123 | Reporting bugs and requesting new features is done through the ticket system. You can view existing tickets, add comments to them and create new tickets using the corresponding buttons at the top of every page. If you want to submit a new bug or request a feature, please use the Search function first to make sure there is no ticket for this task already created. |
| 124 | |
| 125 | Please read the [[Debugging Guide]] for more information on how to gather and provide information to help the developer solve your problem. |
| 126 | |
| 127 | At a minimum, you must include the bldlevel output for the driver you are using. Also, include the PCI Vendor ID and Device ID of your hardware in the ticket (ie. the section from PCI.EXE that relates to your NIC). If the driver traps, please, include the trap screen. |
| 128 | |
| 129 | We review the tickets regularly and leave comments if we need more info. So please revisit the [http://svn.ecomstation.nl/multimac/report/10 Feedback analysis] as often as possible. If we leave comment and don't get feedback from the ticket creator, we will close the ticket after some weeks. |
| 130 | |
| 131 | You must be logged into TRAC to create tickets. Please login with your Netlabs login id. If you do not have a login id, you can request one at http://www.netlabs.org/en/site/member/member.xml. Your login id is created immediately even though there is no indication that it was done. After creating your login, simply go back to the ACPI support page, click Login at the top of the page, and use your new login and password to log in. If you have trouble acquiring a Netlabs login id send an e-mail to Netlabs Community Mailing List. |
| 132 | |
| 133 | Please make sure your name and e-mail address are set correctly in your Preferences. This will ensure that you get an e-mail when your ticket is updated. |
| 134 | |
| 135 | If you fixed a bug yourself and would like your fix to be included in the svn repository, please open a ticket and attach your fix. |
| 136 | |
163 | | = Support and Submitting Tickets = |
164 | | |
165 | | Reporting bugs and requesting new features is done through the ticket system. You can view existing tickets, add comments to them and create new tickets using the corresponding buttons at the top of every page. If you want to submit a new bug or request a feature, please use the Search function first to make sure there is no ticket for this task already created. |
166 | | |
167 | | Please read the [[Debugging Guide]] for more information on how to gather and provide information to help the developer solve your problem. |
168 | | |
169 | | At a minimum, you must include the bldlevel output for the driver you are using. Also, include the PCI Vendor ID and Device ID of your hardware in the ticket (ie. the section from PCI.EXE that relates to your NIC). If the driver traps, please, include the trap screen. |
170 | | |
171 | | We review the tickets regularly and leave comments if we need more info. So please revisit the [http://svn.ecomstation.nl/multimac/report/10 Feedback analysis] as often as possible. If we leave comment and don't get feedback from the ticket creator, we will close the ticket after some weeks. |
172 | | |
173 | | You must be logged into TRAC to create tickets. Please login with your Netlabs login id. If you do not have a login id, you can request one at http://www.netlabs.org/en/site/member/member.xml. Your login id is created immediately even though there is no indication that it was done. After creating your login, simply go back to the ACPI support page, click Login at the top of the page, and use your new login and password to log in. If you have trouble acquiring a Netlabs login id send an e-mail to Netlabs Community Mailing List. |
174 | | |
175 | | Please make sure your name and e-mail address are set correctly in your Preferences. This will ensure that you get an e-mail when your ticket is updated. |
176 | | |
177 | | If you fixed a bug yourself and would like your fix to be included in the svn repository, please open a ticket and attach your fix. |
178 | | |