Tracker Issue Processes

Tracker issue Life-cycle

attachment:process.gif

Please refer to section on roles for further description of roles.

Each square denotes a process which is described below. in the process description you can find time when information should be updated by who and and who is responsible for the completion of the process.

Creation of a Tracker Issue

Any one with access to the internet can in princip create an Issue Tracker in form of a Bug, a Feature Request or a Patch.

It is important to give enough information when the tracker issue is created. Especially for person that do not have a user account, it is hard to complement a Issue Tracker later. This is due to the way that GForge works, and therefore not in our power to change.

Please remmember ALWAYS to:

• For bugs: BR Please Add log files under field "Attach Files:" if you describe an error that can be traced in log files (see below).

• In case you are not a user: BR Please write who you are.

Creation of a Bug

Choose the Bug Tracker in case you want to report a bug which should be implemented as a fix in NetarchiveSuite.

include logs (examples from new deploy)

... <to be written>

Creation of a Feature Request

Choose the Feature Request Tracker in case you want to report a feature request which you would like to have implemented in NetarchiveSuite. The rest of the process is the same as for Bugs, please refer to the Reporting a Bug section.

Creation of a Patch

Choose the Patch Tracker in case you want to report a patch to inclusions in NetarchiveSuite.

... <to be written>

Evaluation of a Tracker Issue

Collect Info.

Prioritization

Implementation of a Tracker Issue

time when information should be updated, by who and when ... <to be written>

Implementing/fixing a Bug

<to be written>

Implementing a Feature Request

<to be written>

Implementing/including a Patch

<to be written>

QA of a Tracker Issue

Release of a Tracker Issue

Release Test

Development Release

Stable Release