The “fix in version” is what we are using to label the version that the issue should be fixed in. It’s a planning tool at this point for us to know what order to work on things in. By “field” I just meant “one of the many values in the Jira ticket” (like an OO “field”, where the ticket is the Object).
I honestly don’t know if that’s the proper use of “fix in version”; I inherited that usage from prior Jira tickets! ☺ From: Gregg Reynolds [mailto:d...@mobileink.com] Sent: Thursday, June 28, 2018 1:32 PM To: Heldt-Sheller, Nathan <nathan.heldt-shel...@intel.com> Cc: Wouter van der Beek (wovander) <wovan...@cisco.com>; Mats Wichmann <m...@wichmann.us>; iotivity-dev@lists.iotivity.org Subject: Re: [dev] please create "Bangkok Point Release" version in JIRA On Tue, Jun 26, 2018, 11:02 AM Nathan Heldt-Sheller <nathan.heldt-shel...@intel.com<mailto:nathan.heldt-shel...@intel.com>> wrote: Thanks guys for raising those points. A few things: 1) We haven't traditionally used "1.4.1" in the "fix in version" field because we normally don't know what the actual numbering will be until after we need the designation. What does "fix in version" mean? What does "field" mean? Honestly I have no idea. G -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9747): https://lists.iotivity.org/g/iotivity-dev/message/9747 Mute This Topic: https://lists.iotivity.org/mt/22303136/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
