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. For example, right now, all we know is that we want a few of the listed Jira bugs to be fixed in the Bangkok Point release, but whether that's 1.4.1, or 1.5, or 1.4.3 (because we find we have to make a few bug fix releases prior) is not yet known. In the past, ISC has worked with BSC (I think) to determine IoTivity versioning. If I had my say, it would simply align with the specification version it is certifiable against, perhaps with an additional minor version for bug fix releases... but that approach was rejected for reasons unknown to me (as I've historically been "just a security guy"). So with the ISC less involved, and me taking more of a role is OSWG, we might revisit this decision soon... but for now we'll stick with what we know (or don't know as the case may be, haha). I'll follow up with a few people who might have more context.
2) The release info pages on wiki are badly out of date and need to be fixed. I have started working with a new volunteer to spin him up on the release mgmt. function but for now, they remain outdated. I have a TODO item on my list to at least make the more recent release info pages "not wrong". It's about 30 items down at the moment, but I'll fix it when we make the 1.4.0 release (which is as soon as we close out the remaining P1 issues). 3) Any time you find anything glaringly wrong in the wiki, feel free to edit! You're not going to make it worse than glaringly wrong :) I'll circle back when I have more info on #1. Thanks, Nathan -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Wouter van der Beek via Lists.Iotivity.Org Sent: Tuesday, June 26, 2018 7:44 AM To: Mats Wichmann <[email protected]>; [email protected] Cc: [email protected] Subject: Re: [dev] please create "Bangkok Point Release" version in JIRA Hi Mats, Thanks for pointing that out. I changed the data in that page. It now refers to OCF2.0. And we need to add more features that has been implemented. I have to talk to Nathan to fill in the actual dates. But we can do that when the actual release is made. Kind Regards, Wouter -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Mats Wichmann Sent: Tuesday, June 26, 2018 2:51 PM To: [email protected] Subject: Re: [dev] please create "Bangkok Point Release" version in JIRA On 06/26/2018 04:14 AM, Wouter van der Beek via Lists.Iotivity.Org wrote: > The official OCF version for the Bangkok release will be 2.0 And the > so called point releases will be 2.0.x > > If IoTivity wants to call it 1.4, that is fine, but then we need a > translation table somewhere in the Wiki. That's a great point. We should have the translation table anyway. My observation was only about the the release values in the iotivity bugtracker, but the code itself is tagged 1.4 (currently in git 1.4.0-RC1 and 1.4.0-RC2) exist and various filled in fields will also make it look like 1.4. I know nothing about the making of that choice so not making any effort to argue about it. Definitely need to make clear that iotivity 1.4 implements the OCF 2.0 specifications. We should clean up things a little bit... the wiki has a page _named_ https://wiki.iotivity.org/2.0_release_plan, which instead contains the 1.3 release planning materials (!), and no information that a search turns up on 1.4 (we've had that discussion previously - there wasn't anybody available to fill this function on a fulltime basis, thanks for the guys who have stepped in when it "isn't their job"), so we're definitely light at the moment on what release numbers mean. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9745): https://lists.iotivity.org/g/iotivity-dev/message/9745 Mute This Topic: https://lists.iotivity.org/mt/22303136/21656 Group Owner: [email protected] Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
