[dev] 2.1.0 release: suggestion for new branching plan

Hi IoTivity Devs, In the past, we've had a relatively unstable master branch, which has caused us to stick to release branches perhaps longer than we'd like, to avoid battling a constant stream of regressions. These long-lived branches entail more work cherry picking release branch changes int

Re: [dev] how to share "same platform ID" among iotivity stack instances?

Hi Kevin, Yes, same .dat file. If you read here: https://wiki.iotivity.org/security_resource_manager?s[]=json2cbor, you’ll find more info about the .dat file and manufacturer defaults. There’s also more info regarding the

Re: [dev] Inefficient code reviews

Yeah I'm not clear about those reports either... but for example since my name doesn't appear at all and I can think of at least a few commits I've done, it's not showing everything. Either way as I mentioned, the report is showing several folks who haven't contributed in years, so it's not t

Re: [dev] Inefficient code reviews

On 09/05/2018 01:35 PM, Heldt-Sheller, Nathan wrote: > Thanks Mats. These graphs don't really show the primary contributors > recently, though, because those are often (mostly?) working on release > branches, not master! It's not as grim as it looks... most of the folks on > those graphs have

Re: [dev] Inefficient code reviews

Thanks Mats. These graphs don't really show the primary contributors recently, though, because those are often (mostly?) working on release branches, not master! It's not as grim as it looks... most of the folks on those graphs have been gone a long time, because work on master was superceded

Re: [dev] Inefficient code reviews

On 09/05/2018 11:27 AM, Nash, George wrote: > Typically the best way to find who to add to your reviews is to use "git > blame" find out who else worked on the file you are modifying. These are the > people that know the most about that code. Add them. Many of them are no > longer active but it

Re: [dev] Inefficient code reviews

Typically the best way to find who to add to your reviews is to use "git blame" find out who else worked on the file you are modifying. These are the people that know the most about that code. Add them. Many of them are no longer active but it does not hurt to add them as reviewers. Look at wh

Re: [dev] how to share "same platform ID" among iotivity stack instances?

Hi Kevin, To set various properties of the /oic/d and /oic/p resources you can use the following API: C: OCStackResult OCSetPropertyValue(OCPayloadType type, const char *propName, const void *value) defined in ocstack.h C++: OCStackResult OC::OCPlatform::setPropertyValue(OCPayloadType type, c