Not quite; we post v0.3 versions of CRs to Iotivity Dev once approved to do so to get Dev community feedback and interest.
Best, Mark. From: iotivity-dev@lists.iotivity.org [mailto:iotivity-dev@lists.iotivity.org] On Behalf Of Nathan Heldt-Sheller Sent: Tuesday, July 24, 2018 6:18 PM To: Gregg Reynolds <d...@mobileink.com> Cc: iotivity-dev <iotivity-dev@lists.iotivity.org> Subject: Re: [dev] News Yeah, but the OCF specification development and review process definitely requires OCF membership, no way around that for IP reasons etc… so we can’t take that to IoTivity Dev. From: Gregg Reynolds [mailto:d...@mobileink.com] Sent: Tuesday, July 24, 2018 12:50 PM To: Heldt-Sheller, Nathan <nathan.heldt-shel...@intel.com<mailto:nathan.heldt-shel...@intel.com>> Cc: iotivity-dev <iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org>> Subject: Re: [dev] News On Mon, Jul 23, 2018, 7:18 PM Nathan Heldt-Sheller <nathan.heldt-shel...@intel.com<mailto:nathan.heldt-shel...@intel.com>> wrote: Thanks Margaret for pointing out to me that the question wasn’t “why hasn’t IoTivity 2.0 been announced?” but “why hasn’t OCF 2.0 been announced on IoTivity Dev?” My apologies for misreading. The OCF 2.0 announcement to IoTivity Dev will be rolled into the release of the supporting implementation (IoTivity 2.0) which is still not finished. Thanks and sorry to add confusion to confusion, Nat But OCF 2.0 has already been published, even if the publication was not announced. Which is too bad, since it has problems that might have been caught by the community, had they been given the chance. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9805): https://lists.iotivity.org/g/iotivity-dev/message/9805 Mute This Topic: https://lists.iotivity.org/mt/23757849/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
