Changes between Version 4 and Version 5 of TicketLifeCycle

Timestamp:

Jun 30, 2010, 10:08:09 AM (15 years ago)

Author:

Frederico Caldeira Knabben

Comment:

--

TicketLifeCycle

@@ -1 +1 @@
 = Ticket Life Cycle =
 
-As of FCKeditor 2.5, every line of code introduced in the FCKeditor/trunk tree must pass through a more strict review process. This guarantees the overall quality of the code base.
+Every line of code introduced in the CKEditor/trunk tree must pass through a strict review process. This guarantees the overall quality of the code base.
 
-This document describes the life cycle of a ticket in the FCKeditor project.
+This document describes the life cycle of a ticket in the CKEditor project.
 
 == Ticket Creation ==
 
-Anyone is allowed (and invited) to open tickets for every single issue faced in FCKeditor. The [wiki:Bugs Bug Reporting Instructions] and [wiki:Features Feature Request Instructions] pages have more information on how to properly fill new tickets.
+Anyone is allowed (and invited) to open tickets for every single issue faced in CKEditor. The [wiki:Bugs Bug Reporting Instructions] and [wiki:Features Feature Request Instructions] pages have more information on how to properly fill new tickets.
 
 == Clean up ==
@@ -23 +23 @@
  * Mark the ticket with the "WorksForMe" keyword if the bug seems to not be present in the current trunk code. A comment should be added instructing the reporter to check it again and provide more information. A "WorksForMe" ticket expires in 30 days if no action is taken in the ticket, resolving it as "worksforme".
 
- * Resolve the ticket as "invalid" if it does not describe a problem with FCKeditor.
+ * Resolve the ticket as "invalid" if it does not describe a problem with CKEditor.
 
  * Resolve the ticket as "wontfix" in the rare cases that the bug seems valid but there's a specific reason why it should not (or cannot) be fixed. If the reason is something we can't workaround, the "CantFix" keyword should be used.
@@ -29 +29 @@
  * Mark the ticket with the "Pending" keyword, if the ticket does not have enough information to move forward, asking the reporter for more details. A "Pending" ticket expires in 30 days if no action is taken in the ticket.
 
- * Mark the ticket with the "Confirmed" keyword. For browser specific tickets, the relative keyword should be appended: "IE", "IE7", "Firefox", "Safari" and "Opera".
+ * Mark the ticket with the "Confirmed" keyword. For browser specific tickets, the relative keyword should be appended: "IE", "IE6", "IE8", "Firefox", "Firefox2", "WebKit" and "Opera".
 
  * Mark the ticket with the "HasPatch" keyword, if a patch or descriptive code changes is provided, even if not analyzed and reviewed.