| 30 | | We use our [http://sophie2.org/trac/ Trac] to report ant track bugs. The homepage of the Trac project is http://trac.edgewall.org/. |
| 31 | | |
| 32 | | In order to report a new bug, just add a new ticket. Fill the ticket fields obeying the following rules: |
| 33 | | * The name of the ticket should be in capital letters and should start with BUG_, followed by a couple of words briefly describing the bug (e.g. BUG_PRO_LIB_OWN). |
| 34 | | * The description should be short but explanatory. This description will be expanded in the Analysis section of the bug's wiki page. You should link the wiki page in the description. |
| 35 | | * You may leave the Assign to and Priority fields to their defaults. |
| 36 | | * Make sure you have selected ''bug'' in the Type field. |
| 37 | | * Select the current milestone from the drop-down menu and the version (2.0). |
| 38 | | * Select the component this bug belongs to. When unable to tell, select ''uncategorized''. |
| 39 | | * You should estimate the importance of the bug and fill it. |
| 40 | | * Also estimate the effort that it will take to fix the bug. |
| 41 | | * The last thing to add is fill your name in the analysis owners field. |
| 42 | | |
| 43 | | Once you have created the page, you should fill the Analysis section according to [wiki:PLATFORM_STANDARDS_ANALYSIS#BugFix]. |
| 44 | | |
| 45 | | Think well of a category this bug may belong to. Current suggestions are: |
| 46 | | * data loss |
| 47 | | * memory leak |
| 48 | | * low performance |
| 49 | | * regression (previously working feature is now broken), |
| 50 | | * exception causing |
| 51 | | * unexprected behaviour |
| 52 | | |
| 53 | | You may add a new suggestion here. After some bugs are categorized, a new custom field with this category will be added to the Trac in order to ease the bug tracking. |
| | 30 | [[Include(wiki:PLATFORM_STANDARDS_MANUAL_TESTS/Bugs)]] |
