Changes between Version 4 and Version 5 of ReportingBugs

Show
Ignore:
Timestamp:
07/21/06 17:29:32 (3 years ago)
Author:
neukirchen
Comment:

Changed policy for TRex version number when reporting bugs for nightly builds

Legend:

Unmodified
Added
Removed
Modified
  • ReportingBugs

    v4 v5  
    1212 
    1313Once you are sure that you have found a new bug, use ''CREATE NEW ISSUE'' and follow the instructions. 
    14 Use a descriptive ''Summary'' and provide in the ''Description'' section a more detailed description of the bug including instructions how to reproduce the bug.  
    15  
    16 The fields ''Fix Version/s'', ''Original Estimate'' are usually only for developers and should be left empty.  
    17 (If you are reporting a bug for a nightly build, the version number of the nightly build displays in the TRex ''Help''->''About''->''Feature Details'' dialog already shows the version of the upcoming release. Nevertheless, it is recommended to select the version of the latest official release at field ''Affects Version/s'', because your bug will hopefully already be fixed in the upcoming release and it is quite likely that your bug is already contained in the latest release.) 
    18  
    19 In addition to the ''Bug'' issue type, you may also suggest an ''Improvement'' or ''New Feature'' as issue type. The type ''task'' shall only be used for internal changes, e.g. to the Web site, because fixed ''task''s do not appear in the release notes. 
     14 * In addition to the ''Bug'' issue type, you may also suggest an ''Improvement'' or ''New Feature'' as issue type. [[BR]] (All other types are probably only relevant for developers: e.g. the type ''task'' shall only be used for internal changes, e.g. to the Web site, because fixed ''task''s do not appear in the release notes.) 
     15 * Use a descriptive ''Summary''. 
     16 * Provide in the ''Description'' section a more detailed description of the bug including instructions how to reproduce the bug.  
     17 * The ''Priority'' can be left at it's default. 
     18 * Concerning the ''Component/s'' to which your report relates, you can make a guess, e.g. ''Core'' if editing capabilities are concerned, ''Refactoring'' if refactoring are concerned, and ''Automated Code Review'' if marker generation and metrics are concerned. In case of doubt, leave it empty. 
     19 * In the ''Affects Version/s'' you should select the version number displayed in the TRex ''Help''->''About''->''Feature Details'' dialog. [[BR]] (If you are reporting a bug for a nightly build, this means that you will use the version number of the upcoming version.) 
     20 * The fields ''Fix Version/s'', ''Original Estimate'' are usually only for developers and should be left empty.  
    2021 
    2122If you like later-on to add further information you can use the ''Comment'' field at any time.