Changes between Version 9 and Version 10 of TicketSpecs


Ignore:
Timestamp:
Feb 19, 2008, 2:56:22 PM (12 years ago)
Author:
Wojciech Olchawa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TicketSpecs

    v9 v10  
    6161=== Priority ===
    6262
    63 This option allows us to segregate the most important issues from the least important ones. We recommend the to set the priority to '''Normal''' and not to use the '''High''' and '''Low''' options. Of course it is a very important for us to know what Bugs/New Features we should deal with firstly. That is why every ticket is reviewed by someone from the core development team, which sets its priority due to its importance.
     63This option allows us to segregate the most important issues from the least important ones.
     64
     65We recommend the to set the priority to '''Normal''' and not to use the '''High''' and '''Low''' options. Of course it is a very important for us to know what Bugs/New Features we should deal with firstly. That is why every ticket is reviewed by someone from the core development team, which sets its priority due to its importance.
    6466
    6567=== Milestone ===
     68
     69This option is used by the core development team for targeting Bugs and New Features. So for example, if we have confirmed a bug and someone has began to fixing it, we set the Milestone to specify what version will be free of this bug e.g. FCKeditor 2.7 .
     70
     71We recommend no to use this option by reporters and leave this setting for developers. However there are two exception for this recommendation.
     72
     73The reporter is allowed to set the Milestone to '''Opera Compatibility''' and '''Safari Compatibility''' if a Bug or a New Feature regards specifically to Opera and Safari browsers, so you can use this Mielstones when something isn't working or should be done only in those browsers
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy