Hi Uze, Thanks for doing such as excellent job tracking all these issues and concerns and trying to hold to a successful schedule.
In my opinion, as long as people are clear that 1.3.0 cannot be certified as either OIC 1.1 or as OCF 1.0 then it is okay to create the release, as a way to mark a relatively stable reference for OCF 1.0 feature preview, for purposes such as beginning vendor application integration etcetera. I do not object to creating a release, if it is useful for member companies? we want OCF to be adopted and be successful, after all! However I have two concerns: 1. This ?non-certifiable? 1.3.0 may be used as a basis for more than it is intended, and since it is not tested yet against complete 1.0 CTT, I am quite certain it contains issues and gaps with the Specifications and their required behavior, even if we haven?t identified them yet. Are we certain vendors will not ship OCF 1.3.0 based products and create interop issues in the field? 2. I also am concerned that with the Amsterdam schedule being so tight, we will skip ahead and start building Amsterdam on an incomplete foundation of 1.3.0, without first completing OCF 1.0 implementation (including all bug fixes and un-discovered feature gaps). That said I think if we commit to driving hard to close all remaining gaps and bugs with full OCF 1.0 CTT then I don?t see harm in releasing 1.3.0, again if it is useful to member companies to do so. But in my opinion, if we are not very disciplined, I think the above two concerns are likely to cause us trouble down the road. Sincerely, Nathan From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? Sent: Monday, May 22, 2017 10:35 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] Regarding IoTivity 1.3.0 release objective Hi All, Today I heard that there are lots of concern for 1.3.0 release in a hurry. But I'd like to share some background for this. Originally IoTivity has a plan to sync up with spec and certifiction schedule. However, there OCF 1.0 spec has been delayed and eventually this caused the misalignment with CTT final and IoTivity 1.3.0 release.
