--On Thursday, January 19, 2006 12:39 PM -1000 austen <[EMAIL PROTECTED]> wrote:
I also felt weird yesterday when I made a Jira issue for something that I could fix in 5 minutes. I also was torn between making a Jira issue for a fix or if I should just fix the problem. On one hand it probably would be counterproductive to make the issue, but for future releases the Jira log would not show what was done. Should I be associating issues with every commit?
Good question, I think it's still too early to tell yet. Let's just keep gaining experience and see what seems appropriate. For the time being, I think we should all be at least _thinking_ about whether there's a Jira issue, and/or whether one should be attached. Think of it this way: if you've made a fix that produces a non-trivial difference between the last release and the next one, then it should probably have a Jira issue associated with it.
Note that it's fine to have a whole bunch of commits associated with the same Jira issue. So, if you're working on an extension to HackyInstaller, you might want to make one Jira issue that describes the complete extension, and then all of your commits associated with that task get associated to it.
There is a way to update the log message in Subversion: <http://subversion.tigris.org/faq.html#change-log-msg>, so if we make mistakes, we can correct them.
Cheers, Philip
