Milestone
We will look at milestones in more detail shortly, but for now we will see how to
modify them.
Unlike the rest of the fields, milestones can be managed directly
through Trac.
Let's see what is already there:
Trac [/projects/trac/sandbox]> milestone list
Name Due Completed
--------------------------
milestone1
milestone2
milestone3
milestone4
Milestones have a couple of additional attributes: the date they are due and the date
they were completed. These are specified using the format YYYY-MM-DD.
Chapter 5
[ 53 ]
As for the others we have the rename, add, and remove commands. When adding
we can specify a due date in addition to the milestone name. There are also two new
commands: due and completed, which allow us to set the respective attributes of a
given milestone.
Version
The version field allows user to identify a particular release of our project. It could
be argued that Version and Milestone provide the same functionality, which to
a degree is true. However the distinction is: we work toward milestones, while a
version marks where we have been. Another way of looking at it is that a given ticket
describes a defect in version x which we are planning to fix in milestone y.
As with components and milestones, the default list is pretty unimaginative:
Trac [/projects/trac/sandbox]> version list
Name Time
----------
2.
Pages:
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80