NetarchiveSuite|
Size: 287
Comment:
|
Size: 1835
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Implementation of a Tracker Issue == Time when information should be updated, by who and when ... <to be written> |
## page was renamed from Process/Implementation ~-[[Action(edit)]]-~ |
| Line 4: | Line 4: |
| === Implementing/fixing a Bug === <to be written> === Implementing a Feature Request === <to be written> === Implementing/including a Patch === <to be written> |
The Implementation process contains [#ImplementationDescription Description], [#ImplementationPurpose Purpose], [#ImplementationResponsible Responsible], [#ImplementationMethod Method], [#ImplementationTime Time], [#ImplementationInput Input] and [#ImplementationOutput Output]. [[Anchor(ImplementationDescription)]] '''~+Description+~'''[[BR]] Distiguish between Bug/Feature Request and Patch [[Anchor(ImplementationPurpose)]] '''~+Purpose+~'''[[BR]] [[Anchor(ImplementationResponsible)]] '''~+Responsible+~'''[[BR]] [:Process_Role/Task_Holder: Task holder]] according to Iteration plan for iterations tasks or [:Process_Role/Module_Owner: Module Owner]] of new tracker issue for that specific module. [[Anchor(ImplementationMethod)]] '''~+Method+~'''[[BR]] Includes Code review. Please refer to the [:Process/Code_Review:Code Review Process]. Includes Document review. Please refer to the [:Process/Document_Review:Document Review Process]. Includes documentation and sanity check. NOTE: the process needs to be adjusted to introduction of a tool that can assist in the Code Review Process. Must also include follwing in translated form: * Komponentejeren informerer test koordinator omkring rettede bugs, således at disse bugs evt. kan blive en del af release testen. Hvis bugs ikke indgår i release testen vil de blive testet via unit tests. De rettede bugs vil endvidere blive noteret i release test beskrivelsen af test-koordinatoren. * Ved kritiske produktions bugs kan det være nødvendigt at branche den aktuelle released produktionskode. [[Anchor(ImplementationTime)]] '''~+Time+~'''[[BR]] [[Anchor(ImplementationInput)]] '''~+Input+~'''[[BR]] [[Anchor(ImplementationOutput)]] '''~+Output+~'''[[BR]] |
The Implementation process contains [#ImplementationDescription Description], [#ImplementationPurpose Purpose], [#ImplementationResponsible Responsible], [#ImplementationMethod Method], [#ImplementationTime Time], [#ImplementationInput Input] and [#ImplementationOutput Output].
Anchor(ImplementationDescription) DescriptionBR Distiguish between Bug/Feature Request and Patch
Anchor(ImplementationPurpose) PurposeBR
Anchor(ImplementationResponsible) ResponsibleBR [:Process_Role/Task_Holder: Task holder]] according to Iteration plan for iterations tasks or [:Process_Role/Module_Owner: Module Owner]] of new tracker issue for that specific module.
Anchor(ImplementationMethod) MethodBR Includes Code review. Please refer to the [:Process/Code_Review:Code Review Process].
Includes Document review. Please refer to the [:Process/Document_Review:Document Review Process].
Includes documentation and sanity check.
NOTE: the process needs to be adjusted to introduction of a tool that can assist in the Code Review Process.
Must also include follwing in translated form:
- Komponentejeren informerer test koordinator omkring rettede bugs, således at disse bugs evt. kan blive en del af release testen. Hvis bugs ikke indgår i release testen vil de blive testet via unit tests. De rettede bugs vil endvidere blive noteret i release test beskrivelsen af test-koordinatoren.
- Ved kritiske produktions bugs kan det være nødvendigt at branche den aktuelle released produktionskode.
Anchor(ImplementationTime) TimeBR