Using the Issue Tracker

Creating Issues

Choosing an Issue Tracker

perfSONAR consists of multiple components each with their own git repositories and issue tracker. There is also the project issue tracker. The rules below should be followed when trying to decide which issue tracker to use:

• End-users should direct issues to the project issue tracker. The release manager will delegate any user-reported issues to the appropriate software components as needed.
• If a developer finds an issue and it only affects a single component, they may assign it directly to that component's issue tracker
• If an issue is created that spans multiple components, you should create an issue in the project issue tracker and create separate issues in each of the affected component's issue trackers that reference the one in the project issue tracker. You may reference another issue using format described here in the comments of the issue.
• A feature request for a brand new component that does not have its own git repository should be placed in the project issue tracker
• If you are in doubt about under which category above an issue falls, just assign it to the project issue tracker.

Viewing Issues

perfSONAR consists of multiple issue trackers, but Github makes it easy to view and sort them all in one place using the issue dashboard.

Closing Issues

As a developer, when you believe an issue has been fixed and tested you may close an issue. Prior to release each issue will be reviewed and may be re-opened if it is found to be incomplete.