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 chapters describe how fields should be used in OpenSync project.


Short Summary

Try to describe bug 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

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.

Bug Properties

Priority

Priority is set by OpenSync core developers, users can leave this into normal or lower.

highest

Security problem. All efforts are done to fix the bug ASAP.

high
Preventing upcoming release.
normal
low
lowest

Severity

critical

Used when bug causes breach in system security. Requires immediate fix and updated packages for distributions.

major
Used when bug causes data loss and thus real damage.
normal
Used in most cases, most likely in yours too. Don't 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

Milestone where this bug is targeted to be fixed.

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

Add vendor name, device model, rfc (rfc1234), obex, bt, wbxml, http, usb etc.

Cc

Carbon Copy, add emails to keep intrested people updated for changes.