TracDev ToDo List

Release 0.12

Documentation

• get someone to proof read the new pages.
  • mark.m.mcmahon: Do you mean the list of all pages under 0.12/ in TitleIndex?
    • cboos: Yes.
    Would you suggest the following:
    • Review the diff for each page that was copied (spelling, grammar, technical)
    • Review the page as a whole, formatting, etc
      • cboos: Indeed, that would be my preferred way. Spelling and grammar fixes should be done straight ahead, no need to discuss them of course, the same for formatting fixes I suppose. Suggestions for documentation changes, additions or clarifications (or simplifications!) could be done in a variety of ways, just be creative! For example:
        • add a === Discussion section at the bottom, with your remarks or additions
        • add #!div in place with some distinctive style, e.g.

          {{{#!div style="background:#efe"
          Addition: / Rewrite:  / ... 
          }}}
          

          Addition: / Rewrite: / …

        • in place italics may not stand out distinctive enough from the original documentation, you could use [[span(style=background:#efe, Also mention...)]] Also mention…
        • … or much simpler, none of the above, just boldly change the documentation if you think you can make an improvement (we'll notice the change and review the differences anyway)
    • does it make sense to log a bitesize, documentation bug for each doc review task?
      • cboos: I don't think so, I think it'll be more effective to collaborate on the document in place
  • rblank: I would suggest starting with the pages under 0.12, proofread whole pages (spelling, grammar, consistency, obsolete text) and fix things as you go along. You may want to open a single "Documentation review" ticket to document your progress for others potential reviewers (and get attribution!).
• copy the current toplevel pages to 0.11/
• copy the 0.12 pages back to the toplevel pages (merging the recent changes when needed)
• sync the wiki/default-pages in the repos from the t.e.o wiki

Remaining tickets

• some i18n polishing (#8055, #8081) and bug fixing (#8588)
• Basic WikiCreole support #4356
• WikiRename / #1106

Verify this one, not sure yet it's a bug which is still present or a transient error that happened in between updates:

2010-02-26 19:24:14,087 Trac[changeset] WARNING: Diff rendering failed for property svn:mergeinfo with renderer SubversionMergePropertyDiffRenderer:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/trac/versioncontrol/web_ui/changeset.py", line 798, in render_property_diff
    options)
  File "build/bdist.linux-x86_64/egg/trac/versioncontrol/svn_prop.py", line 297, in render_property_diff
    all_revs = set(repos._get_node_revs(spath))
  File "build/bdist.linux-x86_64/egg/trac/versioncontrol/cache.py", line 290, in _get_node_revs
    slast = '%010d' % last
TypeError: int argument required

For later (0.13, …, 1.0)

• Help delegator (ticket:2656#comment:26)
• Database: #6348?, #8443?
• ticket query system:
  • #7026 — 0.13?
• i18n:
  • translation of javascript (#6353, Babel:#110) — 0.12-stable?
  • translation of workflow (#5441) — 0.12-stable or 0.13?
• Version Control:
  • CachedRepository.get_path_history
  • merge type #1492
• #2456 - not too early to start thinking about it seriously
• start experimenting with TracDev/Proposals/MultipleProject
• remove support for pysqlite 1.1.x in source:trunk/db/sqlite_backend.py

Mercurial plugin

• add basic support for cached repo (#8417)
• log --follow-first
• show merge changesets in revision log (#1492)

---

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.