Thanks Uze, Agree fully with your plan to create 1.2.1 release. I suggest that we also create a single patch that can be applied to 1.2.0-based projects, so Vendors do not necessarily have to re-base. That way, there is a good chance that Vendor only needs to apply patch to pass CTT 1.4.
And also agree that next time we must ensure we have complete successful CTT test pass before creating final release. This means we must have a single reference Server device application in order to test against CTT. The ?IUT Simulator? is a great start. Can you (or Sungkyu?) please create a list of features that must be added in IUT Simulator, to allow more complete testing of IoTivity? E.G. PIN-based onboarding UI, etc? Then we can discuss who should implement. Thanks, Nathan From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Monday, November 14, 2016 4:03 AM To: iotivity-dev at lists.iotivity.org Cc: cert_wg at openconnectivity.org; oswg at openconnectivity.org Subject: [dev] IoTivity 1.2.1 Release proposal Hi IoTivity developer. After we released the 1.2.0 version, we found some CTT compliance issues. And I figured out many people want additional patch release version fixing these issues from last week OCF F2F meeting. Let me summary my release proposal as follows. . Version: 1.2.1 . mission : CTT 1.4 alignment (to development with CTT 1.4) Each Maintainer, please send items to be in the 1.2.1 release to me. if you have something beyond CTT1.4 alignment, send items also to me. Anyway, please do not merge new feature into 1.2 rel branch except the mission related patches and bug fixes.
