Hello Uze Please schedule some time for someone to develop the randomly-delayed response to multicast queries.
Em quinta-feira, 17 de novembro de 2016, ?s 04:20:53 PST, ??? escreveu: > Hi All, > > Let me fix the 1.2.1 plan. > Target date is End of this Month(Nov). > CTT compliant issues and bugs will be accepted. > Regarding, small feature required for the product can be also acceptable in > this version. By timeline view, please merge all code by this week. > As I mentioned before, a commit on 1.2-rel need to be accepted by > release function lead, myself also. > For this Patch release, some QA activity will happen specially. Originally > Patch version does not have QA testing except unit test. Regarding QA > Testing we can ask to QA lead.(Sungkyu. Ko) > > BR, Uze Choi > --------- Original Message --------- > Sender : ??? <uzchoi at samsung.com> S6(??)/??/IoT Lab(S/W??)/???? > Date : 2016-11-14 21:03 (GMT+9) > Title : [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. > From the next major/minor release let?s align the OCF schedule to avoid this > kind of discrepancy/gap. Any comment will be welcomed. > > BR, Uze Choi > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
