On May 6, 1:52 pm, Olemis Lang <ole...@gmail.com> wrote: > BTW > > I wanted to know something about this . Let's suppose the plugin > implementing this interface is installed under plugins folder (i.e. > private install), so it's available for that particular Trac env. <snip> > >> - Should be added ? > > > Yes, they should. The new interface was implemented quite long ago, at a > > time when I hadn't yet realized that I had to document such changes. > > Thanks for the reminder. > > > -- Remy >
Just a side note here, what does the dev team use/prefer for documenting this sort of thing. Seems like a perfect use for Doxygen. I am debating whether or not to establish a formal documentation tool set here personally, and Doxygen keeps bubbling to the surface, but I also need to generate end user manuals for products (they are devices, not just software) as well as API dev docs, not just source code documentation. Didn't know if you guys used anything other than discipline and change logs to manage all these changes. There's gotta be a VI plugin for this :D look out, dinosaur coming through -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
