Version 2 (modified by 12 years ago) ( diff ) | ,
---|
Documenting API changes since 1.0.x
The next stable version of Trac will be named 1.2 and will contain the cumulative changes made in the successive 1.1.x releases.
These notes reflect the current status for 1.1.1, in trunk.
Proposed changes are prefixed with an OPEN mark and the paragraph is written in italics.
Summary
- Prerequisites
- Detailed List of Developer Visible Changes
- Other Modifications made to the 1.0 API
- New in the 1.1.1 API
Prerequisites
OPEN Python 2.5 support has been dropped. Only Python versions 2.6 and 2.7 are supported.
Modified Dependencies
jQuery and jQuery UI (bundled)
OPEN The bundled version of jQuery is now 1.x.y instead of 1.7.2 in Trac 1.0-stable.
See jQuery release notes for the corresponding major updates 1.8.
The full minified jQuery UI package is now bundled with Trac.
OPEN The current version is 1.8.x
Babel (optional)
OPEN The internationalization support (i18) for Trac is depending on Babel, version 1.0.
Genshi (mandatory)
OPEN
- Genshi 0.7
- Genshi 0.6.x is still supported(?)
New Dependencies
None!
Detailed List of Developer Visible Changes
Ticket | Summary |
---|---|
#10979 | Allow dynamic variables to be used in a report title and description |
API Changes |
New function |
Component: ticket system (1 match) |
|
Ticket | Summary |
#1942 | [patch] Add support for date type in custom ticket fields |
API Changes |
new |
Component: web frontend (1 match) |
|
Ticket | Summary |
#10976 | Compatibility issue between jQuery UI < 1.8.22 and jQuery 1.8 |
API Changes |
jQuery upgraded to 1.8.3, jQuery UI upgraded to 1.9.2 and jQuery UI Timepicker upgraded to 1.1.1. |
Other Modifications made to the 1.0 API
Database API Changes
Environment.get_db_cnx
has been removed
OPEN
Following the deprecation deprecation made in 0.12, using Environment.get_db_cnx
for obtaining a database connection has now been removed.
One should now only use the context managers for retrieving a database Connection in read or write mode.
- a read-only Connection can be used to form queries:
a
with env.db_query as db: ...
db
instance obtained the above way should only be used for executing SELECT queries - a writable Connection can be used to modify the database content in a transaction:
a
with env.db_transaction as db: ...
db
instance obtained the above way can be used to execute INSERT/UPDATE/DELETE queries; they will be committed when the last such automatic transaction in the control flow completes successfully. See DatabaseApi for the full details.
Environment.db_query()
and Environment.db_transaction()
(1.0)
OPEN
The @with_transaction(env)
/ @env.with_transaction()
decorators introduced in 0.12 which have been deprecated in Trac 1.0 have been removed as well.
New in the 1.1.1 API
Be sure to have a look at the new ApiDocs (for latest trunk).
This is a work in progress - coverage is still not yet complete.