Changes between Version 11 and Version 12 of Bugs


Ignore:
Timestamp:
06/11/15 15:43:47 (2 years ago)
Author:
Anna
Comment:

Minor updates to make it consistent with http://docs.ckeditor.com/#!/guide/dev_issues_tracker

Legend:

Unmodified
Added
Removed
Modified
  • Bugs

    v11 v12  
    55To 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
    66
    7 The demo page is always running the latest CKEditor release, so if you cannot reproduce your issue there, update your editor installation first.
     7The demo page is always running the latest CKEditor release, so if you cannot reproduce your issue there, update your editor installation first. Please note that if the problem was fixed in one of the releases that succeeded the version you are using, you will need to [http://docs.ckeditor.com/#!/guide/dev_upgrade upgrade your CKEditor installation] as we do not backport fixes.
    88
    9 You can also test it on our last "[wiki:SVN#NightlyBuild Nightly Build]": http://nightly.ckeditor.com
     9CKEditor is in active development, so there is a chance that we have already fixed your issue in the current code base. You should thus also test it our last "[wiki:SVN#NightlyBuild Nightly Build]": http://nightly.ckeditor.com
    1010
    1111== Avoid Duplicates ==
     
    1313
    1414== Required Information ==
    15 Please provide the following when reporting new bugs. The more information you provide, the quicker the bug may be solved:
    16  * '''Descriptive summary''' - A "right to the point" phrase that best summarizes the issue that you are experiencing.
    17  * '''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.
    18  * '''Browser and OS''' - Your computer configuration, OS, browser name and version.
     15Please provide the following when reporting new issues. The more information you provide, the quicker the problem may be solved:
     16 * '''Descriptive summary''' - A "right to the point" phrase that best summarizes the issue that you are having.
     17 * '''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 invaluable.
     18 * '''Browser name and OS''' - Your computer configuration, OS, browser name and version.
     19 * '''Editor configuration''' – Your editor version, integration method, editor build (you can attach your `build-config.js` file). If you are using a custom build or the problem only occurs in some specific editor packages, this information is crucial for us.
    1920 * '''Screenshot''' - For interface-related issues an image speaks more than thousands of words.
    20  * '''Sample data''' - For content-related bugs please attach a sample file with the text for testing.
    21  * '''Test case file''' - If possible, attach a Test Case file showing the bug. This is the best way to show us the problem that makes it quicker to solve it.
    22  * '''Build configuration''' - If you are using a custom build or the problem only occurs in some specific editor packages, attach the `build-config.js` file with your editor build configuration.
     21 * '''Sample data''' - For content-related issues please attach a sample file from which we can get the text for testing.
     22 * '''Test case file''' - If possible, attach a test case file showing the issue. This is the best way to show us the problem and make it quicker to solve.
    2323
    2424== Important Notes ==
    25 While filing the bug please bear these important things in mind:
    26  * '''Submit different reports for each bug'''. Do not include more than one bug in the same report.
    27  * The "Priority", "Milestone", and "Assign to" fields are reserved to the core development team.
    28  * '''Avoid using the "Keywords" field''' if you are not 100% sure on what to put there.
     25When filing an issue, please bear these important things in mind:
     26 * '''Submit separate reports for each issue'''. Do not include more than one issue in the same report.
     27 * The "Priority", "Milestone", and "Assign to" fields are reserved for the core development team.
     28 * '''Avoid using the "Keywords" field''' if you are not 100% sure what to put there.
    2929 * Make sure you are '''using the latest version of CKEditor'''. Maybe your bug has already been fixed.
    3030 * The '''"Version" field should be used to point the version where the problem occurred for the first time'''. If you cannot assess it, just set it to the version in which you are experiencing the issue.
© 2003 – 2017 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy