Hi
Yes I noticed some headers could be needed (for logging, sec)
but were not installed so I send patches for that,
and then I was suggested by Dan to use experimental namespace,
to move them back in place, I believe those API should be stabilized.
and/or specified somewhere.
You can read more about this discussion in related reviews/or linked bugs:
https://gerrit.iotivity.org/gerrit/21195
https://gerrit.iotivity.org/gerrit/21549
And this (last?) open one:
https://gerrit.iotivity.org/gerrit/#/c/21193/
Talking about namespaces,
your feedback about
using /usr/include/iotivity for headers
is welcome at :
https://gerrit.iotivity.org/gerrit/#/c/8137/
Regards
On 18/08/17 01:53, Nash, George wrote:
Gregg,
The ‘experimental’ directories is a result of a conversation that was
held here on iotivity-dev a while ago. We wanted a way to introduce
new features that we felt did not have enough developer exposure to
really harden the API. It is still feature complete. We want a way to
give the developer community access to new features but leave us the
freedom to change the APIs without going through a deprecation process.
The decision was to use the term ‘experimental’ it makes it clear that
it could change but is more complete than ‘alpha’ or ‘beta’ code.
I hope that answers the question. Since I have not put anything in
‘experimental’ directories I will leave it to anyone else that feels
my explanation needs more clarification.
George Nash
*From:*[email protected]
[mailto:[email protected]] *On Behalf Of *Gregg
Reynolds
*Sent:* Thursday, August 17, 2017 12:49 PM
*To:* [email protected]
*Subject:* [dev] experimental?
i'm seeing a bunch of 'experimental' dirs in the 1.3 source tree?
wassup with that? if it's experimental, what is it doing in a release?
--
mailto:[email protected] gpg:0x467094BC
https://blogs.s-osg.org/author/pcoval/
_______________________________________________
iotivity-dev mailing list
[email protected]
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
