> You should also definitely talk to Emmanuel Blot (eblot). He wrote the > original notification system and I believe he has been considering > extending it.
Actually, I did not wrote it: I mostly fixed some bugs in the notification format so that Trac complies with RFCs and it works with most MUAs (email clients). Notification subsystem needs a major rewrite, and the last time "we" talk about it (many months ago) IChangeListener interface was to be used to replace the current notification architecture. There was already to many changes scheduled for 0.11, so it has been decided to postpone notification changes to the next release (0.12). However, before starting any work on the notification architecture, we need to go through the very long list of notification enhancement tickets (and suggestions about the various roles of notification-related options and fields). This is required to define which features should be left in the Trac core, which API(s) should be offered to plugins, etc. The notification option set also needs to be cleaned up and simplify. Another big change is to move system-wide settings to user settings. Notification in 0.12 is likely to break compatibility with previous release of Trac (both from an API perspective and from a configuration perspective). Cheers, Manu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
