I would like to know what is the process for deprecation. On past projects that I have worked on we had a clearly specified deprecation process. Once a feature or API was deprecated it was marked deprecated in the code using paragmas, markup, or whatever means was needed. If it tells the compiler its deprecated then that’s the best. Then the code would still be supported for a year. Support meant it would continue to build and pass any tests that were in place to test the code before it was deprecated. After a year it would go into non-supported mode. It would remain for at least one more release but would not have any guarantees. It would typically still build but who know what it would do beyond that. After that it could be removed at any point. Note: exceptions to the deprecation policy were made based on security concerns.
I would like to see a similar policy go in for IoTivity. Since there is no deprecation policy I really don’t know how the direct pairing code should be handled. George Nash From: [email protected] [mailto:[email protected]] On Behalf Of Gregg Reynolds Sent: Thursday, August 17, 2017 12:02 PM To: [email protected] Subject: [dev] direct pairing i see direct pairing has been deprecated. is is safe to remove the direct pairing code from csdk security?
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
