Changes between Version 48 and Version 49 of BugReportingGuidelines

Timestamp:

09/27/10 21:45:33 (15 years ago)

Author:

Pat Tressel

Comment:

--

BugReportingGuidelines

@@ -11 +11 @@
 You'll be running your own server and reporting bugs and feature requests based on that.
 
-=== How to report a bug ===
- * We use Trac to manage bugs.
-   * Report a [http://eden.sahanafoundation.org/newticket new bug].
-   * Search for [http://eden.sahanafoundation.org/search existing bugs].
-   * [/report Trac] is the primary repository for reporting of bugs.
+=== How to report a bug or request a feature ===
+ * We use Trac to manage bugs and feature requests.
+   * Report a [/newticket new bug].
+   * Search for [/search existing bugs].
+   * See a [/report list of active bugs].
    * [https://bugs.launchpad.net/sahana LaunchPad] also has some tickets logged.
  * You don't have to be logged in on Trac to report bugs, but...
    * If you are not logged in, be sure to solve the little arithmetic problem that serves as a Captcha to keep out bots.  If you see a page with "System offline" when you connect to Trac, it means Trac thinks you're a bot and has banned your IP address.  Contact us on the sahana-eden@googlegroups.com mailing list or on IRC channel #sahana-eden on freenode.net if this happens.
-   * You can [http://eden.sahanafoundation.org/register register for an account].
+   * You can [/register register for an account].
  * Please check to see if the bug you've found has already been reported.
  * Please provide full details to reproduce the problem, like the example below.
  * Be clear on which system your test is run against - e.g. http://demo.eden.sahanafoundation.org.
- * You may also wish to check the [https://code.launchpad.net/~flavour/sahana-eden/trunk Commit Logs] to see if they can see the Bug being fixed.
+ * You may also wish to check the [https://code.launchpad.net/~flavour/sahana-eden/trunk Commit Logs] to see if the bug is being fixed. (Note to bug fixers -- please accept the bug and say you're working on it.)
  * '''Screenshots''' are good for showing the main problem screen if hard to explain, however, if you get a ticket, then simply the ticket ID would be better than a screenshot, as can simply copy/paste to find the relevant ticket)
  * If the bug is relatively simple to resolve, please add the keywork  "easy", so it will appear on the [http://eden.sahanafoundation.org/report/18 Easy Bugs for Beginners] Report.