Hi, About jira cleanup, I would suggest to add tags if no feedbacks and eventually each of us will keep an eye on his tag,
I've been doing the same for gerrit, I add labels on incoming reviews. The subset I use is: tizen, build, csdk, security, connectivity, depending on where the files are. Hope this save time for all. On 24/03/17 01:23, Dave Thaler wrote: > > *From:*iotivity-dev-bounces at lists.iotivity.org > [mailto:iotivity-dev-bounces at lists.iotivity.org] *On Behalf Of *Nash, > George > *Sent:* Thursday, March 23, 2017 1:41 PM > *To:* Christian Gran <gran at lynxtechnology.com>; > iotivity-dev at lists.iotivity.org > *Subject:* Re: [dev] Jira cleanup > > <https://jira.iotivity.org/browse/IOT-601> > > > C and C++ SDKs need to compile with GCC options > {{-fvisibility=hidden -fvisibility-inlines-hidden}} > > Try a prevent polluting the global symbol space for the linker. > > Phil, as Ubuntu sub-maintainer, do you have a recommendation on the > disposition of IOT-601? > I replied on tracker, is there anything that prevent us to do it on master branch ? > https://jira.iotivity.org/browse/IOT-347 > > > Building documentation not documented > > Is the wiki documentation enough to satisfy this ticket? If so it can > be closed https://wiki.iotivity.org/generate_api_doc if not it still > needs improvement. > I shared a build script to create a doc package: https://jira.iotivity.org/browse/IOT-347 maybe this could be built by CI too ? Waiting for feedback on tracker too Regards -- mailto:philippe.coval at osg.samsung.com gpg:0x467094BC https://blogs.s-osg.org/author/pcoval/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/7485e0ac/attachment.html>
