One of the goal of Iotivity also is OCF compliant code. Moreover, OCF BoD decision has been done by technical consideration.
BR, Uze Choi -----Original Message----- From: Thiago Macieira [mailto:[email protected]] Sent: Tuesday, September 20, 2016 11:32 AM To: ???(Uze Choi) Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] [Action Request] RE: Request to revert the merged patches(#11227, #10743) On ter?a-feira, 20 de setembro de 2016 11:25:03 PDT ???(Uze Choi) wrote: > By definition, right. > However, during release CC, we decided to wait little bit more to come > in for some module. That should not have happened. Everything must be present before RC1. If we come to the time to create the branch and we don't have everything we wanted to have, either we postpone feature freeze and branching (which pushes the RCs and the final release date) or we bump the feature to the next release. It's ok to wait for the next release. It will come within 4 or 5 months. There may be exceptions to that rule. But I would expect any feature freeze exceptions to be discussed on the mailing list. And the proponents of that feature need to request the exception BEFORE the feature freeze. > Furthermore, additional security related patch regarding today OCF BoD > decision will be included soon to align with Spec and to prepare the > plugfest. OCF BoD decisions do not apply to IoTivity. A patch must stand on its own technical merits. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
