SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 67 | Next

David J Murphy

"Managing Software Development with Trac and Subversion"


In Chapter 1 we briefly discussed using priorities in task management, where we
said that using them for task management was personal choice. If we choose to
use them in out project, we should modify this list to reflect the priorities we have
decided to use.
Tracking Our Tasks
[ 52 ]
Component
Component is used to differentiate between different parts of a project. For example,
we may have client and server components. We should customize the contents of
this field to reflect the structure of our project.
As before, seeing the list of defined components is easy:
Trac [/projects/trac/sandbox]> component list
Name Owner
--------------------
component1 somebody
component2 somebody
Unlike the last two though, components have an extra field??”Owner. If we assign an
owner to a component, and a ticket is marked as relating to that component then that
ticket will be assigned to that person.
Components have the rename, add, remove, and chown commands. The first three
behave similarly to the equivalent commands for the other fields, except that we can
specify an owner when adding a component. The new chown command behaves like
its UNIX namesake??”it allows us to change ownership of a component, and takes
two arguments: the name of the component and the new owner.


Pages:
55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79