Guidelines on API Changes
- Always try to maintain API compatibility.
- If an interface must be changed, try to maintain the old interface for at least one minor (eg. 0.10 -> 0.11) version change and log deprecation warnings when it's used. Document the API change in TracDev/ApiChanges/<version>.
- If the old interface can't be maintained, document it as such in the appropriate TracDev/ApiChanges/<version> Wiki page.
Documented Changes
Development Milestones
Milestone 0.11
- r6805: functional tests available in trunk (see TESTING-README)
- r6572: enabled the "noConflict" mode for jQuery, so that other Javascript libraries using '$' in a special way can be used. As a result, plugins using jQuery should be updated (follow the advice in http://trac.edgewall.org/changeset/6572#file11). Whether this change will stay or be reverted is under discussion. update: well, the change has actually been reverted without much discussion in r6715.
- r6352 removed the req.warning("...") call. Replace it with add_warning(req, "...").
- r6139 integrated the API changes developed in the context-refactoring branch. The early 0.11dev plugins most probably need to be adapted. See the TracDev/ApiChanges/0.11 page.
- r5514: Flexible permission system
- r5378: Flexible/extensible ticket workflow
- r4819: Setuptools integration
- r4095: WebAdmin integration
- r4561: versioncontrol "blame" support
- r3947: jQuery integration
- r3935: Timezone support and internal use of datetime
- r3832: Genshi integration (open tickets)
