Hi,
On our road to 0.10, it seems that we are half-way:
* Support for database and version control backends as third-party
plugins
* Improved notification system
* Advanced diff support
* InterWiki support
* todo:
o MySQL database support
o Use WSGI as web-frontend protocol
o Hooks for spam filtering
I think that we now have good feeling about the stability of 0.9.3
(and probably of 0.9.4dev); it's maybe time to move forward.
As we did during the 0.9pre era, we should experiment our own stuff
before making a release, and I would suggest doing it incrementally:
As there are already 4 out 6(*) major items planned for 0.10 in trunk,
I think it makes sense to expose them to a wider audience.
Besides, the introduction of TracDiff features on p.e.c will ease
the code review process. Each "branch" Wiki page could contain
a diff link:
diff:trunk@<last-base-rev-for-the-branch>//sandbox/<branch>
That link would lead to a changeset page showing the exact set of
changes that the branch introduces.
Also, the introduction of InterTrac links would make it easier to
reference to other Tracs from p.e.c Trac:
"H" and "hacks" for Trac Hacks, "pysqlite", "psycopg" for
initrd.org Tracs, etc.
-- Christian
(*) I don't think MySQL support counts here, as I suppose we won't
try it on p.e.c anyway.
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
