During every development activity, problems that need to be resolved are identified. This could be either during initial development, or during a review of existing developed content. These identified problems are regarded as issues. An issue may be reported by anyone.
The PLCSlib Sourceforge project uses a "Tracker", which supports both the creation of an issue, as well as the documentation of the actions taken to resolve them and their current numbers and respective status. In order to have access to the tracker, the developer must be a registered Sourceforge user.
The following trackers, with categories, are available:
The governance of issues is managed by the PLCS Change Control Board. Its relation to the OASIS PLCS TC is shown in Figure 2.
Issue Status | Used to track status of Issue |
Open | Issue raised |
Closed | Issue resolved |
Pending | Issue addressed but solution not signed off |
Deleted | Issue deleted |
#160; | #160; |
Issue Resolution | Used to track issues resolution |
Accepted | CCB accepted issue, assigned to a resource and set Group to a release so will be addressed |
Rejected | CCB rejected issue |
Later | CCB accepted issue , but no resource available, Group set to none |
Fixed | Issue addressed, change reviewed and accepted |
#160; | #160; |
Issue Group | Used to track releases issues assigned to |
None | Issue not assigned to a release |
R1 | CCB accepted issue and assigned to a release R1 |
The process for raising and processing issues is shown in Figure 3.
Email lists
RSS
When an issue has been identified, it needs to be properly reported in order for the other members of the PLCS organisation to be able to track the actions taken to resolve the issue.
Before adding an issue to any of the trackers, it is useful to look through the existing issues. This reduces the chance of the same problem being described as more than one issue.
These steps are needed in order to add an issue to a tracker:
The trackers should be the place where technical discussions concerning issues take place. Discussions in e-mail are much harder to go back to when trying to understand what led to a particular solution to a specific problem and should therefore be avoided. The following steps are needed to comment on an open issue:
When actions has taken to resolve the problem being registered as an issue that includes modifying any of the PLCSlib files, the following steps should be taken.
(while committing the changed file)
(at the Sourceforge tracker)