Changeset 29e0ac3 in rtems-docs


Ignore:
Timestamp:
Aug 12, 2019, 1:43:39 PM (11 days ago)
Author:
Sebastian Huber <sebastian.huber@…>
Branches:
master
Children:
5d7921b
Parents:
926a622
git-author:
Sebastian Huber <sebastian.huber@…> (08/12/19 13:43:39)
git-committer:
Sebastian Huber <sebastian.huber@…> (08/14/19 05:26:56)
Message:

user: Update bug reporting section

Include information from

https://devel.rtems.org/wiki/NewTicket

File:
1 edited

Legend:

Unmodified
Added
Removed
  • user/support/bugs.rst

    r926a622 r29e0ac3  
    8383bug report.
    8484
    85 * Provide a useful single line summary.
     85* Provide a useful single line **Summary**.
    8686
    8787* Use `WikiFormatting <https://devel.rtems.org/wiki/WikiFormatting>`_ to
     
    134134* Write separate bug reports for different bugs.
    135135
    136 * Select a *Type* for the ticket.  Use ``defect`` for a bug.  Note ``infra`` is
    137   used to report issues with the RTEMS servers at OSUOSL.
    138 
    139 * Select a *Version* for the ticket.  This should be the first RTEMS version
     136* Select a **Type** for the ticket.
     137
     138  * Use ``defect`` for a bug.
     139
     140  * Use ``enhancement`` for a feature request in the software or an addition to
     141    the documentation.
     142
     143  * Note ``infra`` is used to report issues with the RTEMS servers at OSUOSL.
     144
     145* Select a **Version** for the ticket.  This should be the first RTEMS version
    140146  which is affected by this bug.  If this is the current Git master branch use
    141147  the version of the next release.  Please provide the exact version of RTEMS
     
    145151  are not interesting.
    146152
    147 * Select a *Component* for the ticket.  Use ``unspecified`` if you are unsure.
    148 
    149 * Select a *Severity* for the ticket.
    150 
    151 * The fields *Milestone* and *Priority* will be most likely set by an RTEMS
     153* Select a **Component** for the ticket.  Use ``unspecified`` if you are unsure.
     154
     155* Select a **Severity** for the ticket.
     156
     157* The fields **Milestone** and **Priority** will be most likely set by an RTEMS
    152158  maintainer.
    153159
    154 * You can relate your new bug to existing bugs through the *Blocked by* and
    155   *Blocking* fields.
     160* You can relate your new bug to existing bugs through the **Blocked by** and
     161  **Blocking** fields.
     162
     163* If you have any external files, such as screenshots or examples, please
     164  *attach* these as files to the ticket.  *Do not use external hosting* because
     165  if you do use external hosting, then our historical record is broken when
     166  those files are no longer available.
     167
     168* Some fields should only be set by the maintainers, as it is not always clear
     169  what they should be set to.  Feel free to make your own choices.
    156170
    157171When you have checked that your report meets the criteria for a good bug
     
    178192* the bug is not reproducible at all,
    179193
    180 * the RTEMS version is quite old and no longer used by RTEMS maintainers,
     194* the RTEMS version is quite old and no longer used by RTEMS maintainers, or
    181195
    182196* fixing the bug has a low priority for others.
Note: See TracChangeset for help on using the changeset viewer.