Re:Document the Why
by ZoFreX on Wednesday March 06, 2013 @04:33PM
(#5334130)
Another way to achieve this goal is to include a ticket number in any commit relating to it. That way you can easily find out why the changes had to be made at that time (assuming your tickets have good descriptions - they do, right?)
[ Parent
| on HN ]
Oh yes, very much so. As I use it, a Ticket can carry, as necessary:
o A discovery and progress narrative, useful to regain working context after long interruption, fit neither for inline comments nor VCS commit comments.
o A research and reference document list
o A related Ticket reference list
o A summary recovery plan and record
o A summary integration plan and record