On Apr 6, 2017 3:46 PM, "Mats Wichmann" <mats at wichmann.us> wrote:
On 04/06/2017 02:27 PM, Dave Thaler wrote: > Well not having experimental stuff in the main branch would be a change to current practice as there?s lots of stuff today that I would claim is experimental. > I would have no objection to such a change, but it might be hard to get others to agree with it. > > From: Gregg Reynolds [mailto:dev at mobileink.com] > Sent: Thursday, April 6, 2017 12:47 PM > To: Daniel Mihai <Daniel.Mihai at microsoft.com> > Cc: uzchoi at samsung.com; Dave Thaler <dthaler at microsoft.com>; iotivity-dev at lists.iotivity.org; Mats Wichmann <mats at wichmann.us> > Subject: Re: [dev] Public and Experimental Public C APIs > > > > On Apr 6, 2017 2:09 PM, "Daniel Mihai via iotivity-dev" < iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>> wrote: > Should we start with the following definitions? > > 1. All C functions included under out/<path_to_IoTivity_SDK>/ are Public APIs > 2. All C functions included under out/<path_to_IoTivity_SDK>/experimental/ are Experimental Public APIs > > wait. the reason we have things like git is because it allows to avoid this sort of thing (among other things). the main branch should _never_ include experimental stuff, IMHO. that's what branches are for. I seem to be missing some of this thread, but... I don't mind a structure that makes it clear what's a "stable" API and what's not, that's great, assuming we're ready to declare anything "stable" at this moment. It's just it all continues to be confusing to me. It you put some code into a new area, let's say I've decided to propose a new directory resource/cloudfoo, and underneath that I've made directories include, examples, src and unittests. ok now i'm confused. isn't just obvious that you would do this on a branch? if it works and everybody likes it, great, we merge it with master. if not, no harm done. i confess i just don't see why anybody sees an issue here. the api is the api, end of story. anything else is, well, somethimg else. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170406/1a368f54/attachment.html>
