R. Andrew Ohana wrote:
Well it is a bit different than other changes, since nothing actually
changes in the ticket itself (which would prompt a notification). Rather
the plugin is just a special render for the branch field, so the merge
is not actually checked until someone actually loads the page for the
first time (results of the merge are cached in the trac database until
invalidated).
If something along these lines were added, it would have to be in the
release management scripts (potentially coupled with a xmlrpc interface
to the trac plugin).
Yep. But any bot able to comment on tickets (or to send mail) could
presumably trigger a recheck when the default milestone changes (i.e.,
upon a release), and hence indirectly (or directly) notify the involved
people if a branch no longer applies.
[How exactly does the cache entry get invalidated? Does is just expire?]
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
