Changes between Version 13 and Version 14 of TracDev/ApiChanges/0.12

Timestamp:

Nov 19, 2009, 10:42:42 PM (14 years ago)

Author:

Remy Blank

Comment:

Added a section about IMilestoneChangeListener.

TracDev/ApiChanges/0.12

@@ -132 +132 @@
 ==== `trac.cache.CacheProxy` ^[source:trunk/trac/cache.py@#L87 (0.12)]^ ==== #CacheProxy
 
-There's a new cache subsystem in [source:trunk/trac/cache.py trac.cache] so that Component instances can cache any data in a safe way. Whenever the cache entry is invalidated, the cached value will be automatically refreshed at the next retrieval, even if the invalidation occurs in a different process. This makes the `config.touch()` trick obsolete.
+There's a new cache subsystem in [source:trunk/trac/cache.py trac.cache] allowing Component instances to cache any data in a safe way. Whenever the cache entry is invalidated, the cached value will be automatically refreshed at the next retrieval, even if the invalidation occurs in a different process. This makes the `config.touch()` trick obsolete.
 
 New decorators:
@@ -138 +138 @@
  - `trac.cache.cached` ^[source:trunk/trac/cache.py@#L65 (0.12)]^ 
 
-See TracDev/Proposals/CacheInvalidation#CacheManager 
+See TracDev/Proposals/CacheInvalidation#CacheManager for details.
 
 === New Interfaces ===
-==== `trac.resource.IResourceManager` ^[source:trunk/trac/resource.py@#L28 (0.12)]^ ==== #IResourceManager
+==== `trac.ticket.api.IMilestoneChangeListener` ^[source:trunk/trac/ticket/api.py@8828:141-157#L140 (0.12)]^ ==== #IMilestoneChangeListener
 
-FIXME: just an example
+Components implementing the `IMilestoneChangeListener` interface are notified upon creation, modification and deletion of milestones. The milestone model object is passed to each handler. Moreover, on modification an additional dictionary is passed, containing the attributes that were modified and their previous values.
+
+See #6543 for details.