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

← Previous Change
Wiki History
Next Change →

Changes between Version 5 and Version 6 of TicketTestsLifeCycle

Timestamp:: Feb 13, 2014, 1:52:14 PM (10 years ago)
Author:: Piotrek Koszuliński
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

TicketTestsLifeCycle

v5	v6
3	3	We use '''Git''' to handle our tests repository. This gives use great flexibility when dealing with test creation and quality assurance. This page describes the way we work with Git when dealing with our bug tickets.
4	4
5		The basic idea is that our "master" branch must remain stable, with all tests PASSing. On the other hand we have several ticket branches that FAIL because of the new unstable tests added to them. See [wiki:CKEditor-Tests.git] for more information on how to work with our tests repository.
	5	The basic idea is that our "master" branch must remain stable, with all tests PASSing.
6	6
7	7	The following is a simplified description of our ticket handling workflow: