Changes between Version 1 and Version 2 of HowToUseTrac
- Timestamp:
- May 7, 2007, 9:14:27 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
HowToUseTrac
v1 v2 1 Trac is basically an issue tracker and ticketing system, similar in principle to Bugzilla. It is a Python app that runs on the server. A large part of the usefulness stems from one feature: there is a commit hook that is called whenever a commit takes place. This allows parsing the commit message, looking for special commands, and thus automatically marking indicated tickets as closed/fixed.1 Trac is basically an issue tracker and ticketing system, similar in principle to Bugzilla. It is a Python app that runs on the server. A large part of the usefulness stems from one feature: there is a commit hook that is called whenever a commit takes place. This allows parsing the commit message, looking for [SpecialCommands special commands], and thus automatically marking indicated tickets as closed/fixed. 2 2 3 3 Workflow is as follows: write up a trac ticket, which is either assigned to someone or accepted by them directly. They can solicit feedback/discussion via comments on that page and use the ticket as a TODO-list (by strikethrough via Wiki formatting of completed items). When committing changes that relate to the ticket, say in the commit message "refs #123". That causes the message to be appended to the ticket as a comment. "closes #123" would do the same and also mark the ticket as closed.
