Changes between Version 27 and Version 28 of TicketSpecs
- Timestamp:
- Oct 29, 2010, 11:14:34 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TabularUnified TicketSpecs
v27 v28 121 121 '''Core Developers Activity''' 122 122 123 - '''[query:keywords~=Discussion Discussion]''' - Tickets that need more discussion to understand the expected behavior, its correct interpretation, the correct way of handling then, etc... 123 124 - '''[query:keywords~=HasPatch HasPatch]''' - Tickets that contains a "valid" (checked by a core developer) proposal patch attached to it. A [report:9 dedicated report] has been created for it. 124 125 - '''[query:keywords~=Review+ Review+]''' - If the patch attached to the ticket is ready to commit 125 - '''[query:keywords~=Review- Review-]''' - When patch added to the ticket is not ready to commit (has bugs or coding style is incorrect. 126 - '''[query:keywords~=Discussion Discussion]''' - Tickets that need more discussion to understand the expected behavior, its correct interpretation, the correct way of handling then, etc... 126 - '''[query:keywords~=Review- Review-]''' - When patch added to the ticket is not ready to commit (has bugs or coding style is incorrect. 127 127 - '''[query:keywords~=Refactoring Refactoring]''' - Tickets are connected with code refactoring to improve code quality 128 128