Changes between Version 139 and Version 140 of TracDev/ToDo

Timestamp:

Jun 11, 2015, 8:56:12 AM (9 years ago)

Author:

figaro

Comment:

First steps towards cleanup

TracDev/ToDo

@@ -3 +3 @@
 = TracDev ToDo List
 
-This page is for improving the clarity of the ongoing development activity in the TracTeam and must be kept short. This is not the place to put your favorite ticket.
+This page clarifies the ongoing development activity in the TracTeam. This is not the place to put your favorite ticket.
  
 == Overview
@@ -16 +16 @@
 Not evaluated: [[TicketQuery(status!=closed,milestone=,format=count)]]
 
-== Keep an eye on contributions
+== Code contributions
 
- - Tickets with **patch** keyword (//initial patch proposed//) \\
+ - Tickets with **patch** keyword (//initial patch proposed//): \\
     By milestone: [[TicketQuery(status=!closed,keywords=~patch,order=priority,milestone=!unscheduled,group=milestone,format=compact)]] 
  - Tickets with **review** keyword (//patch or branch "ready", need some review)//: \\
@@ -26 +26 @@
  - Tickets with no milestone set (//need to be triaged//) {20}:  \\
     [[TicketQuery(status=!closed,milestone=,keywords!~=needinfo|patch,created=1weekago..,format=count)]] new this week, [[TicketQuery(status=!closed,milestone=,keywords!~=needinfo|patch,created=..1weekago,format=count)]] older and [[TicketQuery(type=enhancement,status=!closed,milestone=,keywords=~patch,format=count)]] with patches
-
-We should strive to keep the number of untriaged tickets older than a week down to 0!
 
 == Documentation
@@ -37 +35 @@
 
  - Post-commit hook for pylint report?
- - Big global trailing whitespace clean-up? Can't we do a global `sed 's/ $/$/' file` prior to check-in?
+ - Global trailing whitespace clean-up? Using `reindent.py` already.
 
 == Next Releases
+
+The master list of the next releases is the RoadMap or the [t:roadmap].
 
 === [milestone:next-dev-1.1.x], [milestone:next-major-releases]
@@ -53 +53 @@
 
  - `CachedRepository.get_path_history` (#9775)
- - Show merge changesets in revision log (#3236) ~~`hg log --follow-first` (check, isn't that already done?) ~~ no, seems like follow-first is meaningless; `git log --first-parent` support
+ - Show merge changesets in revision log (#3236), seems like follow-first is meaningless; `git log --first-parent` support
  - Hg: add basic support for cached repo (#8417)
  - __More revisions available__ link at the bottom of revision log, when viewing a partial revision set (#4854).
@@ -61 +61 @@
  - #2456 - users, #5648 - groups
   * i18n
-    - perhaps translation for workflow status and action names (#5441) 
-    - early loading and caching of catalogs (was discussed in #9439)
+    - translation for workflow status and action names (#5441) 
+    - early loading and caching of catalogs (discussed in #9439)
  - Help delegator (ticket:2656#comment:26)
  - #8507 improve explicit gc
@@ -68 +68 @@
 ==== Ticket
 
- * Sort order of tickets in search results: I expected this to be based on the most recent modification time first? It seems it's creation time first.
+ * Sort order of tickets in search results: currently creation time first as opposed to most recent modification time first.
 
 ==== Miscellaneous
@@ -85 +85 @@
 }}}
 
- * In TracInstall#GeneratingtheTraccgi-bindirectory, there's the mention of ''chicken/egg'' problem with `trac-admin deploy`. We should support a direct `trac-admin deploy <target>` call syntax, ie without the need to specify a (dummy) environment.
+ * In TracInstall#GeneratingtheTraccgi-bindirectory there is mention of ''chicken/egg'' problem with `trac-admin deploy`. We should support a direct `trac-admin deploy <target>` call syntax, ie without the need to specify a (dummy) environment.
 
 ----