On Mon, Sep 8, 2014 at 6:26 PM, Ron W <ronw.m...@gmail.com> wrote: > On the fix description side, I put any detail commentary in the source > comments and include a reference to the ticket. Even if you >
In my experience a ticket number is the longest-lasting/maintainable approach (though _all_ of my colleagues complain when i do it, i refuse to remove ticket numbers from code, and i re-add them and raise a ruckus if a fellow coder removes them during "review"). A ticket can be indefinitely extended with new information, which is particularly useful for "big" (large scope/impact) bugs/changes. It also provides the history (including political decisions) of a particular fix/RFE, and doesn't require updating the source code comments every time the specifics of the ticket change. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
