If the bug is fixed, and committed to the appropriate repository (in-time) for the next release, then it is fine to set the fix version.
The only time setting a fix version is bad is when a fix version has be set for a particular release, but has not been committed and subsequently does not make it into the release. With Spring projects, we automate the generation of the changelog based on the fix version in JIRA tickets. So, if the fix version is set prematurely, it is possible that the changelog says a JIRA ticket has been resolved when in fact it has not been; so be careful, especially if/when you automate the generation of the changelog. On Wed, Jan 20, 2016 at 10:30 AM, Dan Smith <[email protected]> wrote: > One question on that is do we fill in the fix version at the time the bug > is fixed, or when the release is made? For example right now we're making > fixes that will probably be in a .M2 release, but there is no .M2 in JIRA > yet. > > -Dan > > On Wed, Jan 20, 2016 at 10:22 AM, John Blum <[email protected]> wrote: > > > With Spring projects, we use "affects" version that an issue was reported > > in (though with Geode not having an official release yet, hmmm). The fix > > (or target) version is the version that the fix will be released in. > > > > On Wed, Jan 20, 2016 at 8:58 AM, Kirk Lund <[email protected]> wrote: > > > > > Darrel and I were just discussing and wondering: What's the current > > > guidelines for the Geode versions that should be specified in the > Affects > > > Versions and Fix Versions of Jira tickets? It's still not clear to me. > > > > > > -Kirk > > > > > > > > > > > -- > > -John > > 503-504-8657 > > john.blum10101 (skype) > > > -- -John 503-504-8657 john.blum10101 (skype)
