|
|
| Line 1: |
Line 1: |
| − | To enter a bug for Slicer, you need to create an account on our bug tracker. Go to http://www.na-mic.org/Bug/ , then click on "Create a new account" at the top of the page. Enter your email address and name, and your temporary password will be sent to your email address. Go back to http://www.na-mic.org/Bug/ and enter your email address and password. Now you will be allowed to add and edit bugs.
| + | <big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [http://www.slicer.org/slicerWiki/index.php/Slicer:Bugs here]</font></big> |
| − | | |
| − | | |
| − | | |
| − | To add a bug, click on "Add a new bug". Choose "Slicer" as the project. Use the Version drop down menu to choose the Slicer version you are reporting the bug for. Include a brief summary in the Summary box, such as "Segfault on OSX when adding new model". If the problem is in a module, try to put the module name in the Summary. In the description area, include as much detail as you can, including what you were doing at the time, if this has worked in the past but is now broken, error messages, any debugging you have tried, links to screenshots, etc.
| |
| − | | |
| − | | |
| − | | |
| − | The Severity and Priority fields are somewhat arbitrary and redundant at this point. Use your best judgement, and these can always been changed later. Fill out the Component, Module, and OS information. If there is additional information about those fields that aren't covered by the drop down menu, put them in the description. Click Submit when you have filled out this information.
| |
| − | | |
| − | | |
| − | | |
| − | Go back to http://www.na-mic.org/Bug/ . The bug you just submitted should be listed under "Five most recently submitted bugs" Click on your bug to edit it further.
| |
| − | | |
| − | | |
| − | | |
| − | You can add additional comments in the "Additional Comments, module author, etc" field, and put your email address in the CC: field to be notified when the bug changes. You can also adjust priorities here as you see fit.
| |
| − | | |
| − | | |
| − | | |
| − | If you want versions, module names, names of developers, etc. to be added, contact Andy Cedilnik at andy.cedilnik@kitware.com and ask him to add new fields to the bug tracker.
| |
| − | | |
| − | | |
| − | | |
| − | When a bug is fixed, go to the [http://splweb.bwh.harvard.edu:8000/cgi-bin/develop/viewcvs.cgi/slicer2/ Slicer Viewcvs], find the file that you edited and submitted to cvs to fix the bug, and click on the file name. You will see something like this:
| |
| − | | |
| − | | |
| − | | |
| − | Revision 1.36.2.6 / (as text) / (view) - annotate - [select for diffs] , Fri May 13 20:18:41 2005 UTC (7 weeks, 4 days ago) by hayes | |
| − | Branch: release-2-5-patches
| |
| − | CVS Tags: release-2-5-dev-patches, release-2-5-dev
| |
| − | Changes since 1.36.2.5: +1 -1 lines
| |
| − | Diff to previous 1.36.2.5 to a branchpoint 1.36
| |
| − | | |
| − | | |
| − | | |
| − | Right click on the Diff (in this case, Diff to previous 1.36.2.5), and select Copy Link Location. Paste this link into the Link to Diff of Fix field on the bug page.
| |
| − | | |
| − | | |
| − | | |
| − | When you resolve a bug, set Status to Closed, and Resolution to fixed.
| |
| − | | |
| − | | |
| − | | |
| − | '''When you edit a bug, make sure to click Submit in the lower right hand corner, or your changes will not be saved!'''
| |
