Currently we tag issues with fixVersion before commit, to indicate what > BRANCHES we intend to commit to, i.e. new features normally gets “master > (9.0)” and 8.2, while bugs normally gets 8.1.2 in addition. More serious > bugs and security issues may in addition be flagged with 7.7.2. >
I tend to use the field to indicate where I *did* port it to and where it can be found. As such I tend not to fill it in until it actually exists there (I 've committed). This avoids issues where a release happens before I have time to complete the fix. I think the "where do I find it" aspect that Mike mentions is more important than automating release notes. (Says the non pmc committer who hasn't had to do a release yet) ;)
