We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

Changes between Version 1 and Version 2 of TicketLifeCycle

Timestamp:: Dec 1, 2007, 3:12:15 PM (16 years ago)
Author:: Alfonso Martínez de Lizarrondo
Comment:: typos

Legend:

: Unmodified
: Added
: Removed
: Modified

TicketLifeCycle

-                      v1
+                      v2
 == Confirming Bugs ==
 Someone from the core development team should them check the ticket information and decide whether it has enough useful information to move forward.
+Someone from the core development team should then check the ticket information and decide whether it has enough useful information to move forward.
 The following actions could be taken when confirming a ticket:
 …
 == Commit ==
 After a patch has been reviewed, someone with commit privileges in the source repository will commit it. The ticket is them resolved as "fixed", pointing to the relative changed with a message like "Fixed with [XYZ].".
+After a patch has been reviewed, someone with commit privileges in the source repository will commit it. The ticket is then resolved as "fixed", pointing to the relative changed with a message like "Fixed with [XYZ].".
 ----