Overview
All rules have their exceptions! The RPT portal "feedback" page is just such an exception. This is the place where RPT client users are allowed, and even encouraged, to communicate back to the RPT developers. The two major avenues:
- Forums.
General information exchange between clients and clients and between clients and developers.
A place to annotate special cases, implementation tricks, "here be dragons" warnings, ... .
- JIRA.
A bug reporting and tracking system.
Can also be used as a "development road-map" (though clients are probably not interested in that aspect).
Forums
Forums are based on the ??? technology. Detailed information about how these forums work can be found at:
- <link-0>. The web site for the product.
- <link-1>. SLAC's implementation of this technology and guidelines for it's use.
The top level the RPT portal's forum space can be accessed <here>
JIRA
JIRA is another Atlassian product and can be tightly tied to the Confluence system. For general information about how JIRA works:
- <link-0>. The web site for the product.
- <link-1>. SLAC's implementation of this technology and guidelines for it's use.
To get the best out of a bug report, please remember than contextual information is very important. Compare a bug report that says, essentially, "It broke" with a bug report that lists:
- Date the problem occurred.
- Host machine and its operating system (if the bug involves using a host machine).
- Target machine (or specific processor within an RPT target) and its operating system.
- Terminal dumps (where available).
- Memory dump (host and/or target, as appropriate).
- Code map (where various pieces of code are loaded in memory ... if available).
- Trace of recent activity (very useful for multi-threaded real-time environments ... if available).
With that in mind, the JIRA project for reporting client RPT bugs can be found <here>.