Changes between Version 9 and Version 10 of Bugs


Ignore:
Timestamp:
Mar 15, 2011, 3:18:56 PM (8 years ago)
Author:
Anna Tomanek
Comment:

Text enhancement and proof-reading

Legend:

Unmodified
Added
Removed
Modified
  • Bugs

    v9 v10  
    11= Bug Reporting Instructions =
     2If you feel you found a bug in CKEditor, we will be grateful for letting us know.
     3
     4== Reproduce on Demo Page ==
     5To eliminate the chance that the issue might be caused by some third-party software or your customizations, try to reproduce the bug on the demo page first: http://ckeditor.com/demo
    26
    37== Avoid Duplicates ==
     8Before you file a new ticket, make sure your bug has not been already reported. Use the search field (at the top of this page) to check it.
    49
    5 Be sure your bug has not been already reported. Use the search field (at the top of this page) to check it.
    6 
    7 You should also test it at our last "[wiki:SVN#NightlyBuild Nightly Build]":[[BR]]
     10You should also test it on our last "[wiki:SVN#NightlyBuild Nightly Build]":[[BR]]
    811http://nightly.ckeditor.com/demo
    912
    1013== Required Information ==
    11 
    12 Please provide the following when reporting new bugs. As more info you provide, as quicker the bug may be solved:
    13 
    14  * '''Descriptive summary''' : A "right to the point" phrase.
    15  * '''Steps to reproduce''' : This is the most important thing. We are not able to fix a bug if we can't see it with our own eyes. A numbered list of actions to reproduce the issue is quite useful.
    16  * '''Browser name and OS''' : You computer configuration, OS, browser name and version.
    17  * '''Screenshot''' : For interface related issues, an image says more than thousands of words.
    18  * '''Sample data''' : For content related bugs, please attach a sample file from which we can get the text for testing.
     14Please provide the following when reporting new bugs. The more information you provide, the quicker the bug may be solved:
     15 * '''Descriptive summary''' : A "right to the point" phrase that best summarizes the issue that you are having.
     16 * '''Steps to reproduce''' : This is the most important thing. We are not able to fix a bug if we cannot see it with our own eyes. A numbered list of actions to reproduce the issue is quite useful.
     17 * '''Browser name and OS''' : Your computer configuration, OS, browser name and version.
     18 * '''Screenshot''' : For interface related issues an image speaks more than thousands of words.
     19 * '''Sample data''' : For content related bugs please attach a sample file from which we can get the text for testing.
    1920 * '''Test case file''' : If possible, attach a Test Case file showing the bug. This is the best way to show us the problem, making it quicker to solve it.
    2021
    2122== Important ==
    22 
    23  * '''Submit different reports for each bug'''. Don't include more than one bug in the same report.
    24  * The "Priority", "Milestone", and "Assign to" fields are reserved to the core team.
    25  * '''Avoid using the "Keywords" field''', if you are not 100% sure on what to have there.
    26  * Be sure you are '''using the latest version of CKEditor'''. Maybe your bug has already been fixed.
    27  * For a full guide how to properly report a new bug go to [wiki:TicketSpecs]
     23While filing the bug please bear these important things in mind:
     24 * '''Submit different reports for each bug'''. Do not include more than one bug in the same report.
     25 * The "Priority", "Milestone", and "Assign to" fields are reserved to the core development team.
     26 * '''Avoid using the "Keywords" field''' if you are not 100% sure on what to put there.
     27 * Make sure you are '''using the latest version of CKEditor'''. Maybe your bug has already been fixed.
     28 * For a full guide on how to properly report a new bug go to the [wiki:TicketSpecs] page.
    2829
    2930== Reporting a Bug ==
    30 
    3131{{{
    3232#!html
    3333<div style="color:red">
    34 <b>Be sure you have read the above instructions before clicking the following link!</b>
     34<b>Before clicking the following link, make sure you have read the instructions above!</b>
    3535</div>
    3636}}}
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy