We should have the $NEXT version tag already created in JIRA. Then it makes sense to mark it directly when that fix is merged to develop.
Anthony > On 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) >>
signature.asc
Description: Message signed with OpenPGP using GPGMail
