On Mon, 2006-04-03 at 11:11 -0400, Sommers, Elizabeth wrote: > >From my boss: > > > I want Trac to use files in Subversion (or any full WebDAV service) as its > store of issues and their associated data (attachments, audit trails, etc.) > Look up SubIssue on tigris.org. Subversion is really a filesystem where > each file has properties, and can be "dialed back" to previous revisions *of > the whole tree at once*. That means that issue changes can be committed in > the same transaction as the source code changes that they document. Did > that bug exist in r3219? Dial back and build from source, and test it. Did > we know about that bug in r3219? Dial back and look in the issue store. > >
How would the user interface for committing changes to tickets at the same time as code changes work? That to me seems like being very difficult to make work nicely from the user's point of view, since your code changes will take place from your local working copy, while the ticket change happens on the trac interface. Unless you have some spooky hook scripts running. But having hook scripts that make changes to the repository is not recommended. Sounds to me like an idea that is nice at the superficial level but impractical when it comes down to thinking about it more deeply. > > > ____________________________ > http://www.pragmatics.com > _______________________________________________ > Trac mailing list > Trac@lists.edgewall.com > http://lists.edgewall.com/mailman/listinfo/trac -- Russ _______________________________________________ Trac mailing list Trac@lists.edgewall.com http://lists.edgewall.com/mailman/listinfo/trac
