We should integrate them into the processes
described in this book wherever we feel they are appropriate.
Once our changes have been merged into the trunk, our ticket can be marked as
resolved, and to close the loop within Trac, a comment should be added, which
makes reference to the revision that resulted from the merge. Using comments in
this way means that we can used the interlinking feature of Trac to link our ticket to
the revision in the Subversion that contains the changes. We can view this revision
through the code browser in Trac; and by including the ticket number in our commit
log in Subversion, a link will be created between the revision in the code browser
and the tickets that drove the changes.
Now our code is merged and our ticket resolved. Our feature is now complete and
our milestone is a step closer. Now it's time to start on the next one.
Putting It All Together
[ 78 ]
Tagging a Release
When we have completed all the features and bugs for a milestone it is time to
release. This will consist of actions like testing, quality assurance, packaging, and
distribution, but here we are only concerned with one: tagging. This allows us to
capture a snapshot of our Subversion repository at that moment in time that is
subsequently easy to return to.
Pages:
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108