h, George ; Gregg Reynolds
Cc: iotivity-dev
Subject: RE: [dev] Proposed API guidelines
Gregg wrote:
We have branches for this kind of stuff. General rule: nothing goes into a
release that is not production-quality and officially supported. Otherwise what
is the point of having releases at all, i
Wow, interesting discussion erupts!
It's worth remembering that iotivity is different things to different
people. As "an implementation of OCF specifications" one would tend to
a more conservative view of what goes into the codebase. But it is also
used as a foundation to develop features that
gt; *Sent:* Tuesday, January 2, 2018 9:46 PM
> *To:* Dave Thaler <mailto:dtha...@microsoft.com>>
> *Cc:* iotivity-dev <mailto:iotivity-dev@lists.iotivity.org>>
> *Subject:* Re: [dev] Proposed API guidelines
>
>
&g
More below…
>
>
>
> *From:* Nash, George [mailto:george.n...@intel.com]
> *Sent:* Wednesday, January 3, 2018 1:37 PM
> *To:* Gregg Reynolds ; Dave Thaler <
> dtha...@microsoft.com>
> *Cc:* iotivity-dev
> *Subject:* RE: [dev] Proposed API guidelines
>
>
>
>
'Nash, George' ; Gregg Reynolds
Cc: iotivity-dev
Subject: RE: [dev] Proposed API guidelines
Gregg wrote:
We have branches for this kind of stuff. General rule: nothing goes into a
release that is not production-quality and officially supported. Otherwise what
is the point of having
On Wed, Jan 3, 2018 at 3:49 PM, Dave Thaler wrote:
> Below
>
>
>
> *From:* Gregg Reynolds [mailto:d...@mobileink.com]
> *Sent:* Tuesday, January 2, 2018 9:46 PM
> *To:* Dave Thaler
> *Cc:* iotivity-dev
> *Subject:* Re: [dev] Proposed API guidelines
>
>
>
: iotivity-dev
Subject: RE: [dev] Proposed API guidelines
> The whole concept of "experimental API" makes little sense to me. "Release
> with experimental (i.e. non-production) APIs" strikes me as an oxymoron.
> We have branches for this kind of stuff. General rule: n
On Wed, Jan 3, 2018 at 3:36 PM, Nash, George wrote:
> > The whole concept of "experimental API" makes little sense to me.
> "Release with experimental (i.e. non-production) APIs" strikes me as an
> oxymoron.
>
>
>
> > We have branches for this kind of stuff. General rule: nothing goes into
> a re
Below
From: Gregg Reynolds [mailto:d...@mobileink.com]
Sent: Tuesday, January 2, 2018 9:46 PM
To: Dave Thaler
Cc: iotivity-dev
Subject: Re: [dev] Proposed API guidelines
On Aug 18, 2017 10:55 AM, "Dave Thaler via iotivity-dev"
mailto:iotivity-dev@lists.iotivity.org>> wrote
Below
From: Gregg Reynolds [mailto:d...@mobileink.com]
Sent: Tuesday, January 2, 2018 9:17 PM
To: Dave Thaler
Cc: iotivity-dev
Subject: Re: [dev] Proposed API guidelines
On Jan 2, 2018 7:18 PM, "Dave Thaler via iotivity-dev"
mailto:iotivity-dev@lists.iotivity.org>> wrote:
2018 9:46 PM
To: Dave Thaler
Cc: iotivity-dev
Subject: Re: [dev] Proposed API guidelines
On Aug 18, 2017 10:55 AM, "Dave Thaler via iotivity-dev"
mailto:iotivity-dev@lists.iotivity.org>> wrote:
As the new API maintainer, here’s a set of proposed API guidelines.
Please review so a
On Aug 18, 2017 10:55 AM, "Dave Thaler via iotivity-dev" <
iotivity-dev@lists.iotivity.org> wrote:
As the new API maintainer, here’s a set of proposed API guidelines.
Please review so and feedback can be incorporated before making official
guidelines.
1 APIs
--
There are three types of A
On Jan 2, 2018 7:18 PM, "Dave Thaler via iotivity-dev" <
iotivity-dev@lists.iotivity.org> wrote:
Two new proposed API guidelines, please review:
* A public API should not be added to Iotivity if there is already a
non-deprecated API that can just as easily be used (i.e., with
approximately the sa
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Mats Wichmann
Sent: Friday, August 18, 2017 9:35 AM
To: iotivity-dev@lists.iotivity.org
Subject: Re: [dev] Proposed API guidelines
On 08/18/2017 09:54 AM, Dave Thaler via iotivity-dev wrote:
> As the new API maintainer, here's
blem: the behavior of the old test should never change.
IoTivity would add new tests, for the new behavior, but continue to test the
old behavior too.
Dan
From: iotivity-dev-boun...@lists.iotivity.org
on behalf of Mats Wichmann
Sent: Friday, August 18, 2017 9:34 AM
To: iotivity-dev@lists.iotivi
On 08/18/2017 09:54 AM, Dave Thaler via iotivity-dev wrote:
> As the new API maintainer, here's a set of proposed API guidelines.
> Please review so and feedback can be incorporated before making official
> guidelines.
> 1.3 Internal APIs
> -
> Internal APIs are considered to be u
As the new API maintainer, here's a set of proposed API guidelines.
Please review so and feedback can be incorporated before making official
guidelines.
1 APIs
--
There are three types of APIs:
1) Public
2) Experimental
3) Internal
1.1 Public APIs
---
Public APIs are
17 matches
Mail list logo
