NetarchiveSuite|
Size: 2245
Comment:
|
← Revision 44 as of 2010-08-16 10:24:51 ⇥
Size: 2087
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from Process/Tracker Issue Lifecycle ## page was renamed from Process/TrackerIssueLifeCycle |
|
| Line 2: | Line 4: |
| = Tracker Issue Processes = | <<Action(edit)>> |
| Line 4: | Line 6: |
| == Tracker issue Life-cycle == attachment:process.gif |
The tracker issue life cycle processes for bugs, feature requests and patches contains [[#TILCLifeCycle|Life-Cycle]], [[#TILCMonitoring|Monitoring]]. Each part is presented in diagramatical form where squares denotes processes and the responsible role is indicated with a small drawing. The diagrams are accompanied with a table with links to the referred processes and roles. |
| Line 7: | Line 8: |
| Please refer to section on roles for further description of roles. | <<Anchor(TILCLifeCycle)>> '''~+Life-Cycle+~'''<<BR>> Below you find a diagram of the tracker issue life-cycle, followed by references to processes and roles. |
| Line 9: | Line 12: |
| 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. |
{{attachment:process_Tracker_Issue_Lifecycle.gif}} |
| Line 12: | Line 14: |
| == 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. |
||'''Processes''' ||'''Roles''' || ||[[Process/Create Tracker Issue|Creation]] || {{attachment:module_owner.gif}} [[Process Role/Module Owner|Module Owner]] || ||[[Process/Evaluate Tracker Issue|Evaluation]] || {{attachment:qa.gif}} [[Process Role/QA Coordinator|Quality Assurance Coordinator]] || ||[[Process/Collect Info on Tracker Issue|Collect Needed Info.]] || {{attachment:task_holder.gif}} [[Process Role/Task Holder|Task Holder]] || ||[[Process/Prioritization|Prioritization]] || {{attachment:test.gif}} [[Process Role/Test Coordinator|Test Coordinator]] || ||[[Process/Implementation|Implementation]] <<BR>> ~-Includes [[Process/Code Review|Code Review Process]] and [[Process/Document Review|Document Review Process]]-~ || || ||[[Process/QA of Implementation|Quality Assurance]] || || ||[[Process/Release Test|Release Test]] || || ||[[Process/Release|Release]] || || |
| Line 15: | Line 24: |
| 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. | <<Anchor(TILCMonitoring)>> '''~+Monitoring+~'''<<BR>> Below you find a diagram of the tracker issue monitoring followed by references to processes and roles. |
| Line 17: | Line 28: |
| 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. |
{{attachment:process_Tracker_Issue_Lifecycle_qa.gif}} |
| Line 21: | Line 30: |
| === 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 === |
||'''Processes''' ||'''Roles''' || ||[[Process/Monitoring Tracker Issues|Monitoring Tracker Issues]] || {{attachment:qa.gif}} [[Process Role/QA Coordinator|Quality Assurance Coordinator]] || |
The tracker issue life cycle processes for bugs, feature requests and patches contains Life-Cycle, Monitoring. Each part is presented in diagramatical form where squares denotes processes and the responsible role is indicated with a small drawing. The diagrams are accompanied with a table with links to the referred processes and roles.
Life-Cycle
Below you find a diagram of the tracker issue life-cycle, followed by references to processes and roles.
Processes |
Roles |
Implementation |
|
|
|
|
|
|
Monitoring
Below you find a diagram of the tracker issue monitoring followed by references to processes and roles.
Processes |
Roles |