Changes between Version 135 and Version 136 of TracDev/ToDo

Timestamp:

Feb 8, 2015, 2:49:26 PM (9 years ago)

Author:

figaro

Comment:

Cosmetic changes, added "See also" links

TracDev/ToDo

@@ -2 +2 @@
 = 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.
+ 
 == Overview
+
 ||                ||= **Urgent** ||= Not Urgent ||
 ||= **Important**     || \
@@ -26 +29 @@
 
 == Documentation
+
  - Update the [[TracL10N]] documentation for new-style Transifex DONE ->[[TracL10N/Transifex]] 
  - Finish Sphinx ApiDocs
@@ -31 +35 @@
 == Code clean-up
 
- - post-commit hook for pylint report?
- - big global trailing whitespace clean-up?
+ - Post-commit hook for pylint report?
+ - Big global trailing whitespace clean-up?
 
 == Next Releases
@@ -41 +45 @@
 
 ==== Wiki
+
  - #1132, #3021 and GenericTrac, attacking it from the wiki side...
    - #31 and #886 (experimental repos:ticket-links)
@@ -49 +54 @@
 
  - `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) ~~`hg log --follow-first` (check, isn't that already done?) ~~ no, 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 actually)
@@ -65 +70 @@
 ==== Ticket
 
- * **sort order of tickets in search results**: I expected this to be based on the most recent modification time first? It's seems it's creation time first...
-
+ * Sort order of tickets in search results: I expected this to be based on the most recent modification time first? It's seems it's creation time first.
 
 ==== Miscellaneous
@@ -85 +89 @@
  * In TracInstall#GeneratingtheTraccgi-bindirectory, there's the mention of ''chicken/egg'' problem with `trac-admin deploy`. I've been bitten by this as well and I think we should support a direct `trac-admin deploy <target>` call syntax, i.e. without the need to specify a (dummy) environment.
 
-
-
-
 ----
-''To editors: this is not the place where to put your favorite ticket (see SeaChange/WhatUsersWant instead); this page must be kept short and is mainly for improving the clarity of the ongoing development activity in the TracTeam.''
+See also: SeaChange/WhatUsersWant, [http://trac.edgewall.org/wiki/ToDo ToDo], TracProject/ToDo