Devs (in particular, committers), I'm noticing a fair number of JIRA issues which are left open after work has been logged on them (commits have been pushed). These represent two cases: 1. The problem was fixed / work was completed, but nobody resolved the issue in JIRA. 2. An intermediate commit was made which does not complete the work. These typically involve adding additional logging to help debug.
For #1, all I can do is say: please remember to close your issues after pushing your changes (with the proper fixVersion set for the branches in which it was applied). Release managers should double check for open issues with work logged prior to releasing. For #2, I think what is best is that if you need to add additional logging/debug messages, please create a sub-task for improving the logging and commit those improvements under the sub-task issue. That way, we can close that issue when it is completed, even if the parent issue isn't yet complete. (unless somebody has a better suggestion) Doing these two things will help ensure that our CHANGES / release notes actually reflect the work which was done in a tagged release and prevent discrepancies between JIRA and the git history. -- Christopher L Tubbs II http://gravatar.com/ctubbsii
