587
Comment:
|
← Revision 10 as of 2010-08-16 10:24:54 ⇥
589
converted to 1.6 markup
|
Deletions are marked like this. | Additions are marked like this. |
Line 2: | Line 2: |
[[Action(edit)]] | <<Action(edit)>> |
Line 4: | Line 4: |
The !NetarchiveSuite bug/feature-request/patch registration is done by '''''tracker issues''''' in [https://gforge.statsbiblioteket.dk/tracker/?group_id=7 GForge] | The !NetarchiveSuite bug/feature-request/patch registration is done by '''''tracker issues''''' in [[https://gforge.statsbiblioteket.dk/tracker/?group_id=7|GForge]] |
Line 8: | Line 8: |
1. Reporting Process for tracker issues [[BR]] An overview of the tracker issue lifecycle is given and each part of the lifecycle is explained. 1. Fields that can appear in tracker issues [[BR]] An overview is given including what is displayed and editable both for user logged in and not logged in to GForge. [[BR]] |
1. Reporting Process for tracker issues <<BR>> An overview of the tracker issue lifecycle is given and each part of the lifecycle is explained. 1. Fields that can appear in tracker issues <<BR>> An overview is given including what is displayed and editable both for user logged in and not logged in to GForge. <<BR>> |
Introduction
The NetarchiveSuite bug/feature-request/patch registration is done by tracker issues in GForge
The tracker issues are explained in three different ways:
Reporting Process for tracker issues
An overview of the tracker issue lifecycle is given and each part of the lifecycle is explained.Fields that can appear in tracker issues
An overview is given including what is displayed and editable both for user logged in and not logged in to GForge.