NetarchiveSuite|
Size: 1304
Comment:
|
Size: 3420
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == 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. |
~-[[Action(edit)]]-~ |
| Line 4: | Line 3: |
| 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. | The Creation of a Tracker Issue process contains [#CreateTIDescription Description], [#CreateTIPurpose Purpose], [#CreateTIResponsible Responsible], [#CreateTIthod Method], [#CreateTITime Time], [#CreateTIInput Input] and [#CreateTIOutput Output]. |
| Line 6: | Line 5: |
| 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. |
[[Anchor(CreateTIDescription)]] '''~+Description+~'''[[BR]] Anyone with access to the internet can create a Tracker Issue in form of a Bug, a Feature Request or a Patch. |
| Line 10: | Line 9: |
| === 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. |
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 13: | Line 11: |
| include logs (examples from new deploy) | 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. |
| Line 15: | Line 16: |
| ... <to be written> | [[Anchor(CreateTIPurpose)]] '''~+Purpose+~'''[[BR]] 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 17: | Line 20: |
| === 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. |
[[Anchor(CreateTIResponsible)]] '''~+Responsible+~'''[[BR]] Anybody |
| Line 20: | Line 24: |
| === Creation of a Patch === Choose the Patch Tracker in case you want to report a patch to inclusions in !NetarchiveSuite. |
[[Anchor(CreateTIMethod)]] '''~+Method+~'''[[BR]] * Classify your issue as a bug, feature request or a patch * a '''bug''', if the issue is concerned with an error in the !NetarchiveSuite package, e.g. a spelling error * a '''feature request''', if the issue represents a suggested change in the !NetarchiveSuite package, e.g. a better interface * a '''patch''', in case it includes explicit changes and/or additions to the !NetarchiveSuite package, e.g. new translation files. * Go to tracker issue in !NetarchiveSuite GForge matching your issue classification ([http://gforge.statsbiblioteket.dk/tracker/?atid=105&group_id=7&func=browse bugs], [http://gforge.statsbiblioteket.dk/tracker/?atid=108&group_id=7&func=browse feature request], [https://gforge.statsbiblioteket.dk/tracker/?atid=107&group_id=7&func=browse patch]) and click 'Submit New'. * Fill in the fields (described under [http://netarchive.dk/suite/BugInfGuide/Fields Fields for different Tracker Issues] marked with "new"). [[BR]] Most importantly are the fields: * [:BugInfGuide/Fields#Summary:FieldSummary] * must also name of reporting person, in case you are not a user in the system. * must also include version, if it does not exist in the drop down list for the 'Version' field * Detailed description: * Attach Files - where * logs must be attached in case of a bug * files with updates/additions must be attached in case of a patch * Version . If known it is desireble if the fields 'Assigned To', 'Module' are set. [[BR]] Fileds like 'Priority', 'Status' and 'Duplicate Of:' will '''''rarely''''' be set at creation time. |
| Line 23: | Line 42: |
| ... <to be written> | '''''Include logs (examples from new deploy)''''' [[Anchor(CreateTITime)]] '''~+Time+~'''[[BR]] Any time [[Anchor(CreateTIInput)]] '''~+Input+~'''[[BR]] Any issue to be reported as a bug, a feature request of a patch. [[Anchor(CreateTIOutput)]] '''~+Output+~'''[[BR]] A '''new''' Tracker issue registered in the !NetarchiveSuite GForge tracker system. |
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
- Classify your issue as a bug, feature request or a patch
a bug, if the issue is concerned with an error in the NetarchiveSuite package, e.g. a spelling error
a feature request, if the issue represents a suggested change in the NetarchiveSuite package, e.g. a better interface
a patch, in case it includes explicit changes and/or additions to the NetarchiveSuite package, e.g. new translation files.
Go to tracker issue in NetarchiveSuite GForge matching your issue classification ([http://gforge.statsbiblioteket.dk/tracker/?atid=105&group_id=7&func=browse bugs], [http://gforge.statsbiblioteket.dk/tracker/?atid=108&group_id=7&func=browse feature request], [https://gforge.statsbiblioteket.dk/tracker/?atid=107&group_id=7&func=browse patch]) and click 'Submit New'.
Fill in the fields (described under [http://netarchive.dk/suite/BugInfGuide/Fields Fields for different Tracker Issues] marked with "new"). BR Most importantly are the fields:
[:BugInfGuide/Fields#Summary:FieldSummary]
- must also name of reporting person, in case you are not a user in the system.
- must also include version, if it does not exist in the drop down list for the 'Version' field
- Detailed description:
- Attach Files - where
- logs must be attached in case of a bug
- files with updates/additions must be attached in case of a patch
- Version
If known it is desireble if the fields 'Assigned To', 'Module' are set. BR Fileds like 'Priority', 'Status' and 'Duplicate Of:' will rarely be set at creation time.
Include logs (examples from new deploy)
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.