Changes between Version 21 and Version 22 of TracTicketTriage

Timestamp:

Nov 30, 2006, 10:06:30 AM (17 years ago)

Author:

ilias@…

Comment:

refactorign keyword, some discussion

TracTicketTriage

@@ -48 +48 @@
    * [query:group=status&keywords~=patch patch] - 
      same as review keyword, but when a patch is created by a third party
+   * [query:group=status&keywords~=refactoring refactoring] - 
+     indicates a refactoring step (e.g. patch) which changes structure but not functionality
+
  - Related to work done in branches
    * [query:group=status&keywords~=setuptools setuptools] - 
@@ -119 +122 @@
 
 '''Section order'''
- * ''ilias'': possibly the sections of the the document should be in the order on which a user hits on the fields (e.g. Ticket Type first).
- * ''sid'': maybe, but you definitely want to convey the most important info first... so priority if information is not necessarily the same order as the tickets appear on the ticket view page.
+ * ''lazaridis'': possibly the sections of the the document should be in the order on which a user hits on the fields (e.g. Ticket Type first).
+   * ''sid'': maybe, but you definitely want to convey the most important info first... so priority if information is not necessarily the same order as the tickets appear on the ticket view page.
+     * ''lazaridis'': ok, seems you are right
 
 '''Keywords on separate page'''
- * ''ilias'': the 'keywords' section should possibly moved out to a separate document
- * ''sid'': I disagree. The keywords is a long section, but I want one page open while I'm working on tickets for reference, not 2.. and I think all on one is a good plan to stick to. If it gets too complicated for 1 page, time to simplify!
+ * ''lazaridis'': the 'keywords' section should possibly moved out to a separate document
+   * ''sid'': I disagree. The keywords is a long section, but I want one page open while I'm working on tickets for reference, not 2.. and I think all on one is a good plan to stick to. If it gets too complicated for 1 page, time to simplify!
+     * ''lazaridis'': 1-page solution is fine. You are right that a long keyword sections indicates the need to simplify, as it's an indication that something is wrong.
 
 '''Policy for closing tickets for outdated Trac releases'''