Changes between Version 76 and Version 77 of BugReportingGuidelines


Ignore:
Timestamp:
04/11/18 23:06:34 (4 years ago)
Author:
Kiarra O
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BugReportingGuidelines

    v76 v77  
    1111
    1212== How to report a bug or request a feature ==
    13 We use Trac to manage bugs and feature requests.
    14  * Before reporting or updating bugs, first [/register register for an account] and log in. (No approval is needed.)
    15  * Report a [/newticket new bug].
    16  * Search for [/search existing bugs].
    17  * See a [/report/34 list of active bugs].
    18  * [https://bugs.launchpad.net/sahana LaunchPad] also has some (very old) tickets logged.
    19  * 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 ([wiki:Chat]) if this happens.
     13We use Github to manage bugs and feature requests.
     14* Before reporting or updating bugs, first [https://github.com/ register for an account] and log in. (Choose the free option)
     15* Go to the issue tracker for Eden.
     16* Search through the existing issues; you can use the Labels dropdown to narrow down your search.
     17* For open bugs make sure in the search it says ‘is:open’.
    2018
    2119Bug reporting guidelines:
    22  * Please check to see if the bug you've found has already been reported.
    23  * Please provide full details to reproduce the problem, like the example below.
    24  * Be clear on which system your test is run against - e.g. http://demo.eden.sahanafoundation.org.
    25  * 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.)
    26  * '''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)
    27  * 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.
    28 
     20* Please check to see if the bug you've found has already been reported.
     21* Please provide full details to reproduce the problem, like the example below.
     22* Be clear on which system your test is run against - e.g.  [http://demo.eden.sahanafoundation.org].
     23* You may also wish to check the [https://github.com/sahana/eden/commits/master 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.)
     24* '''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)
     25* If you are a contributor, be sure to use the correct labels when reporting your bug.
    2926=== For GCI students ===
    3027We will be using [http://sunflower.sahanafoundation.org/eden/default/index Sunflower], Sahana's Community Management portal for reporting bugs.