TracDev ToDo List

Release 0.12

Documentation

• get someone to proof read the new pages, see 0.12/ for guidelines
• copy the current toplevel pages to 0.11/
• copy the 0.12 pages back to the toplevel pages (merging the recent changes when needed)
  • well, maybe even add a trac-admin wiki copy operation first, it could take less time. A rename is not that effective here as we would loose the overall history.
• sync the wiki/default-pages in the repos from the t.e.o wiki

This should be done before the beta.

Remaining tickets

• before the beta
  • verify a MySQL database can be updated from 0.11 to 0.12 (#9138)
  • i18n bug fixing (#8588)
  • basic WikiCreole support #4356
• after the beta
  • some i18n polishing (#8055, #8081)

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

From 0.12/TracBrowser@6:

MMM there is no View revision input field at the top of the Repository Browser page. I found out why. There are actually two views for the repository browser in 0.12 …

a) Before you in a particular repo (​http://localhost/test_env/browser) b) After you are in a particular repo (​http://localhost/test_env/browser/MyProject)

I don't currently know which view it goes to if you only have a default repo.

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.

Release 0.11.7.1

Only a handful of issues.

Maybe take this opportunity to do a last documentation sync before archiving the 0.11 pages.

0.12.1

Bug fixing and performance improvements.

• #8443 if no solution found for 0.12
• #8507 improve explicit gc

0.13

• #4431 and related wiki improvements

For later (…, 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.