From RKWard
Revision as of 09:00, 18 November 2015 by Tfry (Talk | contribs)

Jump to: navigation, search


Reporting bugs or wishes

Thanky you for taking the time to report things that are borken, missing, or should be improved, in RKWard. Before you do, a few basic guides to make sure we can handle your input, efficiently. We'll make it short:

Browsing and commenting on existing bugs and wishes

Please take a minute to check, whether the issue you are about to report has already been reported. You can browse existing open bugs and wishes in the KDE bugtracking system.

At the time of this writing, most existing tickets are still in our old tracker(s) at SourceForge.net: bugs wishes. Please do not create new tickets, there. Tickets will be migrated to our the KDE bugtracking system, as soon as we can find the time for that.

Reporting bugs

  • Whenever possible, use the template provided by Help->Report Bug from within RKWard. This will automatically include a lot of useful information, that is often key to analysing issues.
  • If this is not possible, for some reason (e.g. RKWard is not starting at all), make sure to include information on the following items:
  • the version number of RKWard
  • the version number of R
  • the version number of KDE
  • the operating system
  • the method of installation used (for KDE, R and RKWard; e.g. binary bundle, distributor's packages or compiled from source)
  • what did you do to run into the problem? (if it's running some R code, please consider including example code to reproduce it)
  • how can the problem be reproduced?

Submit this info as a new bug report in the KDE Bugtracking System. Note that you will have to create an account, if you don't have one, yet.

Only if this is not possible for some reason, you can also send your report to our mailing list.

Reporting wishes

  • Please report one wish at a time. Split several issues into several tickets. This make it much easier to manage.
  • Try to make a specific suggestion, not just "Feature XY should be improved". If you cannot quite put your finger on what should be done, do let us know, too, but write to our mailing list, instead of opening a ticket. This is better suited for discussions.
  • While in many cases this information may not be strictly necessary, it is never wrong, and often helpful, to include the output of rk.sessionInfo() in your request.

Subject to the above, submit this info as a new wishlist item in the KDE Bugtracking system. Note that you will have to create an account, if you don't have one, yet.

Personal tools