Differences between revisions 18 and 20 (spanning 2 versions)
⇤ ← Revision 18 as of 2009-01-19 12:43:42 →
Size: 3099
Editor: EldZierau
Comment:
← Revision 20 as of 2009-01-19 12:58:55 → ⇥
Size: 2709
Editor: EldZierau
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
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. Anyone with access to the internet can create a Tracker Issue in form of a Bug, a Feature Request or a Patch.
Line 9: Line 9:
It is important to give enough information when the tracker issue is created. Especially for person who does 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. It is important to give enough information when the tracker issue is created. Especially for person who does not have a user account, it is hard to complement a Tracker Issue later. This is due to the way that GForge works, and therefore not in our power to change.
Line 11: Line 11:
Please remmember ALWAYS to: Please remember ALWAYS to:
Line 18: Line 18:

'''''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>		 To make a formal report of a tracker issue (bug, feature request or patch) in a way that enables tracking of the life-cycle of the issue.
Line 47: Line 31:
 *  * Fill in the fields .... as described ...
 * Include logs (examples from new deploy)
 * Include version and patch files for patches

Action(edit)

The Creation of a Tracker Issue process contains [#CreateTIDescription Description], [#CreateTIPurpose Purpose], [#CreateTIResponsible Responsible], [#CreateTIthod Method], [#CreateTITime Time], [#CreateTIInput Input] and [#CreateTIOutput Output].

Anchor(CreateTIDescription) DescriptionBR Anyone with access to the internet can create a Tracker Issue 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 who does not have a user account, it is hard to complement a Tracker Issue later. This is due to the way that GForge works, and therefore not in our power to change.

Please remember ALWAYS to:

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

  • For bugs: BR Make a remark of version in the 'Summary' field, in case the version is not listed in possible values for the 'Version' field.

  • For non-registered users: BR Write who you are in the 'Summary' field.

Anchor(CreateTIPurpose) PurposeBR To make a formal report of a tracker issue (bug, feature request or patch) in a way that enables tracking of the life-cycle of the issue.

Anchor(CreateTIResponsible) ResponsibleBR Anybody

Anchor(CreateTIMethod) MethodBR

Anchor(CreateTITime) TimeBR Any time

Anchor(CreateTIInput) InputBR Any issue to be reported as a bug, a feature request of a patch.

Anchor(CreateTIOutput) OutputBR A new Tracker issue registered in the NetarchiveSuite GForge tracker system.

Process/Create Tracker Issue WithoutTitle (last edited 2010-08-16 10:24:57 by localhost)