Hello !
I've not been able to try and play with all features in 0.12 .
However, now that CommitTicketUpdater & Co. are (distributed with |
recommended for) 0.12 , and considering that :
- It's integrated with trac-admin , thus solving some of the
(IMHO) main issues with RepositoryHookSystem, i.e.
(the lack of a) global access point for invoking Trac
from inside commit hooks, windows support & ...
- Pluggable hooks architecture is already in core .
- The built-in solution is VCS agnostic
- ...
I was wondering what should be the future of RepositoryHookSystem
plugin . IOW which of the following decisions should (happen | be
made)
- Backport (core devs ;o) Trac 0.12 VCS hooks api to 0.11
- Abandon development of the plugin and mark it as deprecated
- Schedule further (few) remaining features implemented in the
plugin to merged with trunk
- Other ?
I'd really appreciate some feedback 'cause I'd not like spend my time
reinventing the wheel .
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
On adding AMF (RPC) support for Trac -
http://feedproxy.google.com/~r/simelo-en/~3/RDv-qDkEK_w/on-adding-amf-support-trac.html
--
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.
