Opensync Bug Management
Here can be found guidelines for submitting bugs into OpenSync Trac bug database.
Timely basis bugs are reviewed and comments for bug status will be asked from reporter or anyone with similar symptoms. If no comment is received in 30 days, bug will be closed and considered fixed. This is done to keep the bug database valid and valuable tool for development. Feel free to reopen the bug even after closing if seen appropriate.
The following table describes how fields should be used in OpenSync project.
| Ticket description | |||
| field | set by | value | description |
|---|---|---|---|
| Short summary | reporter | text | Try to describe the issue as shortly and clearly as possible. Leave unnecessary information out. People read through long lists and need to get overall picture of your issue with this. |
| Type | reporter | defect | Problem that prevents using software. |
| enhancement | New feature or enhancement, something that doesn't exist yet and is broken. | ||
| task | Task to be done by developers. Not a bug nor enhancement. | ||
| Full description | reporter | text | Please describe what you did, what you expected to happen and what happened Is this problem reproducible? If possible provide instructions on how to reproduce it. What devices, plugins are involved? Did this work before, eg. other mobiles, other versions, ... Are you willing to run tests if asked? |
| Ticket properties | |||
| field | set by | value | description |
| Priority | developer | highest | Security problem. All efforts are done to fix the bug ASAP. |
| high | More important than others: blocks fixing other bugs or testing. | ||
| normal | |||
| low | |||
| lowest | |||
| Severity | reporter | blocker | Preventing upcoming release. |
| crtitical | Bug causes breach in system security. Requires immediate fix and updated packages for distributions. | ||
| major | Bug causes data loss and thus real damage. | ||
| normal | Prevents using the software or missing feature. Used in most cases. Do not cause inflation in higher Severity levels by rising your problem higher than it really is. | ||
| minor | Bugs that doesn't cause failures nor prevent using the software. | ||
| trivial | Missing documentation and other cosmetic non-functional issues. | ||
| Milestone | developer | version # | Milestone where this bug is targeted to be fixed. |
| Version | reporter | version # | Opensync version. In case of SVN checkout, set version and mention revision in comment. If the bug cannot be reproduced in higher version, the version should remain as is. Otherwise it should be changed to the highest reproducible release (and svn revision in comments). |
| Keywords | reporter | text | Add vendor name, device model, rfc (rfc1234), obex, bt, wbxml, http, usb etc. |
| Cc | anyone | trac account email address |
Carbon Copy, add emails to keep intrested people updated for changes. |
Tags used in summary line
Due Trac's limitation not to allow adding customized metadata flags to its tickets opensync.org has ???? to add Summary prefixes so that these flags are visible in ticket listing.
Flags are enclosed into single brackets. There can be more than one flag and in such case the are separated by comma. An example of Summary field would be:
[NEEDINFO,PATCH] Add entry merging feature to osynctool
| tag | stands for |
|---|---|
| NEEDINFO | Ticket triager or developer has asked more information in next 30days. |
| PATCH | Ticket contains a patch. |
| TRIVIAL | An easy task that does not require developer coding skills. |
| WAITNEXT | Problem happened once or seldom, we need to wait for the next time. Action is at Ticket reporter |
