#7763 closed enhancement (wontfix)
Separate subscribers
| Reported by: | Robert Corsaro | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | AnnouncerPlugin |
| Severity: | normal | Keywords: | TracNotification replacement |
| Cc: | Ryan J Ollos, Robert Corsaro | Trac Release: | 0.12 |
Description
We should decide which subscribers are absolutely crucial to replace trac notification and separate them from the "new feature" category of subscribers. We can stick the "new feature" ones in opt. This will allow us to put higher priority on "crucial" subscribers and making sure they are right to get adoption into core trac.
Attachments (0)
Change History (7)
comment:1 Changed 11 years ago by
| Cc: | Ryan J Ollos Robert Corsaro added; anonymous removed |
|---|---|
| Keywords: | TracNotification replacement added; 0.12 removed |
| Owner: | changed from Robert Corsaro to Steffen Hoffmann |
| Summary: | Seperate subscribers → Separate subscribers |
comment:2 Changed 11 years ago by
(In [12338]) TracAnnouncer: Separate "standard" subscribers from "new feature" ones, refs #7763.
"Standard" means required to mimic TracNotification behavior here.
This hasn't been as easy as it might look like now. Thanks to Ryan for hints on missing import of test modules, that started to matter right after trying to execute tests from multiple (sub)directories.
comment:3 Changed 11 years ago by
Developer hint: See http://packages.python.org/distribute/setuptools.html#test-build-package-and-run-a-unittest-suite for more on launching unit tests from setup.py.
comment:4 Changed 11 years ago by
comment:5 Changed 11 years ago by
Why doesn't TicketCommitUpdater work on this ticket twice in a row? Hm, strange.
comment:6 Changed 7 years ago by
| Owner: | Steffen Hoffmann deleted |
|---|
The approach here is a generic divide and rule strategy to me.
I decided to adopt the idea, because I've been a bit uneasy with the rather big collection of subscribers.