Changes between Version 4 and Version 5 of TicketLifeCycle


Ignore:
Timestamp:
Jun 30, 2010, 10:08:09 AM (9 years ago)
Author:
Frederico Caldeira Knabben
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TicketLifeCycle

    v4 v5  
    11= Ticket Life Cycle =
    22
    3 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.
     3Every 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.
    44
    5 This document describes the life cycle of a ticket in the FCKeditor project.
     5This document describes the life cycle of a ticket in the CKEditor project.
    66
    77== Ticket Creation ==
    88
    9 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.
     9Anyone 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.
    1010
    1111== Clean up ==
     
    2323 * 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".
    2424
    25  * Resolve the ticket as "invalid" if it does not describe a problem with FCKeditor.
     25 * Resolve the ticket as "invalid" if it does not describe a problem with CKEditor.
    2626
    2727 * 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.
     
    2929 * 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.
    3030
    31  * Mark the ticket with the "Confirmed" keyword. For browser specific tickets, the relative keyword should be appended: "IE", "IE7", "Firefox", "Safari" and "Opera".
     31 * 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".
    3232
    3333 * Mark the ticket with the "HasPatch" keyword, if a patch or descriptive code changes is provided, even if not analyzed and reviewed.
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy