Bug reports
Bugs can be filed at this address: http://trac.hackable1.org/trac/newticket
Here are some guidelines to help writing them down.
Fields
Priorities
The different priorities are:
- urgent => fix ASAP
- high => fix next thing
- normal => belongs to the masses
- low => can wait
- wait => fix later
Components
The component list will grow as we integrate more elements into the project. The current ones are:
- applications => regular applications
- build => applies to the build system
- packages => applies to the packaging system
- phone => applications related to phoning
- website => problem on the web site
Severities
- blocker => the whole project is broken (does not build...)
- critical => a complete subsystem is affected, security...
- major => a program crashes, data is lost...
- minor => some feature misbehaves...
- trivial => simple issue
Ticket types
- defect => software issue (bug...)
- enhancement => ideas, feature requests...
- task => something new that has to be done
Versions
We have released only one version so far, called "beta". Reports applying to unreleased, SVN sources should be assigned to the "trunk" version (equivalent to HEAD/current...).
Milestones
Regarding milestones, the first is "Phone", because we want to use Hackable:1 as a phone as soon as possible.
Report content
To write down the report content itself:
- try to use short and clear sentences,
- do not modify the bug description after submission, but rather create a wiki page and add a comment linking to it,
- copy and paste full messages and relevant data as often as possible,
- avoid wiki syntax whenever possible, as it looks awful in e-mails.
Common sense
For the rest, common sense and cooperation should do. Don't worry if you don't know exactly which priority/severity/component to choose, someone else will certainly know.
