Reporting Bugs

Like all programs, R3R has bugs. The purpose of this document is to help you efficiently report bugs that you find.

Use a recent build

Before reporting bugs, make sure you're using the latest version and preferably pull the latest changesets from git to make sure your bug hasn't already been fixed.

Make sure it's a bug

  1. Be sure that the feed is being sent out as the right content type. Do not send RSS feeds out as plain text.
  2. If it's an XML-based feed, please validate it.
  3. Be sure that the feed is on a recent version of a server that's compliant with HTTP/1.1. As of the time of writing, Apache 2.x is your best bet. The full response can be found in the cache.

Get Ready

Now, you're almost ready to report the bug. Use the bug tracker at SourceForge after finishing the following check points.

  1. Please be sure that the bug hasn't already been reported.
  2. Collect the information you need on the your operating system, the version of R3R you're using, and the bug category. Keep the bug report brief, but include as much relevant information as possible.
[OSS services provided by SourceForge.]