-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 15.11.2012 09:00, Ryan Ollos wrote:
> On Wed, Nov 14, 2012 at 11:39 PM, Brettschneider Falk
> <[email protected] <mailto:[email protected]>> wrote:
> 
>     > Is it safe to use the latest SVN revision of AnnouncerPlugin?
>     Because I've seen many commits these days, and I don't want to
>     svn-checkout something unfinished.
> 
> 
> I would suggest you avoid using AnnouncerPlugin trunk in production for
> at least a few more weeks or months. I think the 0.11 (1) branch is much
> more stabl. Let's see what hasienda has to say.

Sure. My recent Announcer changeset comments tell you pretty much the
same. I have the old announcer-0.12.1 with some patches in production,
but that limits it to 0.12 and early versions of 0.13dev before the
minor db API changes that are the root cause for the `AttributeError` in
this plugin's db schema version check. Btw, the same issue has been
reported for other plugins as well, i.e. TagsPlugin.

>     Can AnnouncerPlugin provide similar notification behavior like Trac
>     after the switch to that plugin (except my wish for previous
>     updaters)? I don't want to confuse people here used to the current
>     system.
> 
> 
> I think the notification behavior will be very similar if you leave the
> defaults.

Me too.

> I did some brief testing, and it looks like we don't yet have the
> behavior you want (2). It looks like we'll need to add a rule with
> description "notify me when a ticket I updated is modified". I'll defer
> again to hasienda for a final verdict on this one, since I haven't
> worked with that part of the code much yet.

Hm, you're certainly right about that. OTOH this type of implicit
subscription is a rather subtle one, that may be even look accidental to
some less experienced users, so I doubt, that this shortcoming would
become a blocker, if someone attempted a TracNotification --> Announcer
migration. Even more as I found it works not as reliable on t.h.o (near
Trac trunk, past 1.0 now) compared to t-h.o (still at ancient Trac
0.10.6dev).

Hope, this question even gets obsoleted by progress on the TracAnnouncer
proposal.

Steffen Hoffmann

[1] http://trac.edgewall.org/wiki/TracDev/Proposals/Announcer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlCoDzoACgkQ31DJeiZFuHeMBgCgxZZztOxDhHm1CCdCGMKz/Nsu
Zx0AoNm499Rmj4WZZ25aNVakss2ignxq
=x51u
-----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" 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-users?hl=en.

Reply via email to