There is a recent trend in JIRA management where a change being tracked by one JIRA is committed only to master, or maybe master and branch-2, and then the JIRA is left open. The fix versions may or may not be updated. The biggest offender is Ted Yu but newer committers are also occasionally doing it. Ted has no excuse, the rest is understandable.
Please be advised this makes release management difficult. The RM has to look at every commit in the repository and then make sure JIRA reflects the correct fix version. Otherwise the generated change log for the release will be incorrect. If more patches are pending for other branches, and the fix versions are not set correctly, then the RM may miss the patch and not include it into the release. This is the best practice: 1. Set the fix versions for all relevant branches on the JIRA 2. Assemble patches for all relevant branches on the JIRA 3. Commit all of the patches at once to all relevant branches 4. Mark the JIRA resolved I understand there are a lot of branches now, and some changes require backports. In this case, commit the patch at hand to the branches it will apply to, then open a new JIRA (could be as a subtask) for the backport. Make sure to set fix versions appropriately so the RMs will see it. If our slipping JIRA discipline is not improved we will have incorrect release change logs, fewer releases, releases missing changes they should include, and other poor outcomes. -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
