How about a standard syntax for those commits that are "quick fixes"? We could even make a "quick fix" jira issue that everyone case for those special cases. I like this idea, because if every commit was associated with a issue then the possibilities of creating analyses that connect developer activity with jira issues (work and rework/schueduled and unscheduled).
thanks, aaron ----- Original Message ----- From: austen <[EMAIL PROTECTED]> Date: Thursday, January 19, 2006 12:39 pm Subject: Re: [HACKYSTAT-DEV-L] Fixes committed To: [email protected] > 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? > > Cheers, > austen > > On 1/19/06, Philip Johnson <[EMAIL PROTECTED]> wrote: > > I've run freshStart all.junit and everything now looks good. Also > I fixed the bug in > > hackySensor_Vim's sensor.vim.jar file that Julie noticed. > > > > It seemed counterproductive to log a new Jira issue to note the > fixing of a broken build, > > so I tagged it as "[Broken Build]". Upon retrospect, I guess I > could have tagged it as a > > continuation of the old Jira issue that I was working on when I > introduced the bug. Hmm. > > > > Contritely yours, > > Philip > > >
