Date   

Testing mailing list

Thiago Macieira
 

--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center


Test Message

Dieter, William R <william.r.dieter@...>
 

This is a test to make sure people can subscribe to and receive email from the iotivity-dev email list before asking everyone to subscribe.

 

Sorry for the spam.

 

Thanks,

Bill.

 


Re: Test Message

Thiago Macieira
 

On Thursday 04 December 2014 14:50:59 Dieter, William R wrote:
This is a test to make sure people can subscribe to and receive email from
the iotivity-dev email list before asking everyone to subscribe.
It works.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center


Moving 01.org to IoTivity.org

Dieter, William R <william.r.dieter@...>
 

HI All,

Here is a proposed timeline for moving to iotivity.org.  All times are Pacific Standard Time:

1.       Complete processing of existing items in Gerrit on 01.org by Friday December 19th, 9:00 p.m. [all contributors]

a.       Note that this must include all currently outstanding CA and BLE integration patches [Fred Cooper and Uze Choi]

2.       Existing repository (with all active branches) on 01.org are moved to IoTivity.org during the day of Saturday December 20th [Bill Dieter]

3.       Verification of move success completed Saturday December 20th (and Sunday December 21st as needed) [Led by Pat Lankswert with input from contributors]

4.       Contributing teams start using the IoTivity repository on Iotivity.org on Monday December 22nd, 8:00 a.m. [with the repo on 01.org made read-only at that time]

Are there any major objections?

I realize there will be some amount of disruption no matter when the move occurs.  We are hoping that doing it sooner rather than later will be best.

Thanks,
Bill.


Connectivity Abstraction and libcoap

Lankswert, Patrick <patrick.lankswert@...>
 

To all,

 

Please register for the new mailing list at iotivity.org per Thiago and Bill’s guidance.

Please make sure to reply to both the old and new mailing list until the old mailing list is deprecated.

 

Uze and Ashok,

 

I think that it was asked before, but I do not know if I heard an answer. Is there a technical reason that connectivity abstraction uses its own new version of libcoap? The version that was used since M1 has a number of bug fixes and performance improvements that do not seem to be ported to the version used by the connectivity abstraction.

 

Was the existing version lacking?

 

Pat

 

Patrick Lankswert

Intel Corporation

Platform Engineering (PEG) / Wireless Platforms R&D / Wireless Software Solutions (WSS) / Louisville

 


Re: Connectivity Abstraction and libcoap

MyeongGi Jeong <myeong.jeong@...>
 

Dear Pat.

    Hi. how are you ?

    We think that seperation of transport and protocol is better.

    There are multiple reasons for not following existing M1 libcoap.

    1) For long term, it will be beneficial to use the libcoap as it is so that changes can be minimized when we update new features from libcoap opensource.

        i.e. We tried to reduce the dependency between transport and coap protocol.

    2) CA is rewritten completely for WIFI,ETHERENET,BT and BLE adapters for multiple OS platforms such as Ubuntu,Arduino,Android and Tizen.

        If we use libcoap transport, it can cause complexity of source code.

    3) Currently ,libcoap is used only for creating and parsing the coap message . So there will complete modularization.

    if we replace any other messaging such as MQTT or UPnP, there will be minimal changes.

    All the libcoap changes made are incorporated in the current CA architecture.

 

    Thanks.


Best Regards.

/**

 *  @name      MyeongGi Jeong

 *  @office    +82-31-279-9172

 *  @mobile    +82-10-3328-1130

 *  @email     myeong.jeong@...
 */

 

 

 

------- Original Message -------

Sender : Lankswert, Patrick<patrick.lankswert@...>

Date : 2014-12-18 06:20 (GMT+09:00)

Title : [dev] Connectivity Abstraction and libcoap

 

To all,

 

Please register for the new mailing list at iotivity.org per Thiago and Bill’s guidance.

Please make sure to reply to both the old and new mailing list until the old mailing list is deprecated.

 

Uze and Ashok,

 

I think that it was asked before, but I do not know if I heard an answer. Is there a technical reason that connectivity abstraction uses its own new version of libcoap? The version that was used since M1 has a number of bug fixes and performance improvements that do not seem to be ported to the version used by the connectivity abstraction.

 

Was the existing version lacking?

 

Pat

 

Patrick Lankswert

Intel Corporation

Platform Engineering (PEG) / Wireless Platforms R&D / Wireless Software Solutions (WSS) / Louisville

 


Re: Moving 01.org to IoTivity.org

Lankswert, Patrick <patrick.lankswert@...>
 

To all,

Since there were no objectives to this plan, we are moving forward with the transition from 01.org to iotivity.org.

As a group we have committed to using SCONS as our build system moving forward. As such, we will be using the SCONS scripts under Jenkins for builds on build.iotivity.org in the transition from 01.org’s build machines.

Pat

 

From: iotivity-dev-bounces@... [mailto:iotivity-dev-bounces@...] On Behalf Of Dieter, William R
Sent: Wednesday, December 17, 2014 3:47 PM
To: OIC-OSD@...; iotivity-dev@...
Cc: Brian Warner (brian.warner@...)
Subject: [dev] Moving 01.org to IoTivity.org

 

HI All,

Here is a proposed timeline for moving to iotivity.org.  All times are Pacific Standard Time:

1.       Complete processing of existing items in Gerrit on 01.org by Friday December 19th, 9:00 p.m. [all contributors]

a.       Note that this must include all currently outstanding CA and BLE integration patches [Fred Cooper and Uze Choi]

2.       Existing repository (with all active branches) on 01.org are moved to IoTivity.org during the day of Saturday December 20th [Bill Dieter]

3.       Verification of move success completed Saturday December 20th (and Sunday December 21st as needed) [Led by Pat Lankswert with input from contributors]

4.       Contributing teams start using the IoTivity repository on Iotivity.org on Monday December 22nd, 8:00 a.m. [with the repo on 01.org made read-only at that time]

Are there any major objections?

I realize there will be some amount of disruption no matter when the move occurs.  We are hoping that doing it sooner rather than later will be best.

Thanks,
Bill.


Re: Moving 01.org to IoTivity.org

Lankswert, Patrick <patrick.lankswert@...>
 

To all,

This is the last call for M2 submissions. If you are have additional content that you want to be considered for inclusion into the M2 milestone, please send a note to these mailing lists today. We have a lot of code to merge and review and a lot fewer people available over the holidays.

Please remember that we are transitioning the GIT repos to iotivity.org over this weekend. Any pending gerrit reviews will have to resubmitted to gerrit @ iotivity.org.

Pat Lankswert

DCTG Chair and Maintainer


Re: Moving 01.org to IoTivity.org

Lankswert, Patrick <patrick.lankswert@...>
 

To all,

The transition to the GIT repositories at iotivity.org is complete. Please update your local repository references to the new repository.

The repositories at 01.org are still live but are marked read-only and you will not be able to push changesets to that repository any longer.
The build machine at the Linux Foundation needs some additional configuration for unit testing. This is causing continuous integration to report failures. We intend to close this gap as quickly as possible on Monday morning ET. We are sorry for the inconvenience.
Any pending reviews at 01.org will have to be resubmitted to iotivity.org. We are in the process of moving a couple of the pending reviews that we know are important. If we do not move yours and you need help let us know. Please note, that resubmitting drops the existing comments and the list of requested reviewers.

We have tagged the following branches as 0.9.0 release candidates on iotivity.org:
- Master branch: 0.9.0-RC1
- Connectivity Abstraction branch: 0.9.0-CA-RC1
- Control Manager branch: 0.9.0-CM-RC1
- Android Port M2 branch: <untagged>

At this point, I am asking maintainers to hold new feature patches and prioritize fixes as we pull these branches into a single release.

I would like to send thanks to June Yong, Uze Choi and Sudarshan Prasad for their around the clock (and world) assistance and especially Bill Dieter for his GIT planning and heavy lifting.

Pat Lankswert
DCTG Chair and Maintainer


Re: Moving 01.org to IoTivity.org

Dieter, William R <william.r.dieter@...>
 

Here is the current status of the iotivity.org infrastructure:

Item URL Status
------- ---------------- -------------
Web www.iotivity.org Up (access controlled with htaccess)
Wiki wiki.iotivity.org Up (access controlled via IP whitelist for OIC member companies)
Git/Gerrit gerrit.iotivity.org Up (IP whitelist)
Jenkins build.iotivity.org Up (IP whitelist)
Mailing list lists.iotivity.org Up (open to the whole world)
Jira jira.iotivity.org Up (for several weeks)

As a reminder, please update your git remotes to point to iotivity.org:

git remote rename origin oic01
git remote add origin ssh://<username>@gerrit.iotivity.org:29418/iotivity
git branch -u origin/master master

Where <username> is your Linux Foundation ID. Please repeat the "git branch -u" command for each branch that you use, replacing "master" with the branch name (e.g., "git branch -u origin/connectivity-abstraction connectivity-abstraction).

If you had a pending commit in oic-review.01.org, the fastest way to get it moved to iotivity.org is to check out the commit and do

git push origin HEAD:refs/for/<branch>

where <branch> is the branch to which you would like push. Assuming you have updated your remotes, your commit will show up on gerrit.iotivity.org, and can be reviewed as usual.

Verification and Integration builds seem to be working on the build machine using the makefile build process. I apologize for the several build notice emails some of you may have received. Only one commit has been through the verification and integration build process, so there may be additional issues that will not appear until more commits are made. If you run into problems, please send email to iotivity-dev@.... We were not able to get scons to build locally using the directions in the README and did not have time to debug the issue. We will be working on the transition to scons as soon as possible.

Build verification works a little differently than on 01.org. On 01.org, the build machine made a +1 or -1 review, just like human reviewers, based on build results. On iotivity.org, the build machine adds its +1 (or -1) to a separate "Verified" field that is independent of the Code Review provided by people.

Please send all new mailing list traffic to the iotivity-dev mailing list.

Thanks,
Bill.

-----Original Message-----
From: OIC-OSD [mailto:oic-osd-bounces@...] On Behalf Of Lankswert, Patrick
Sent: Sunday, December 21, 2014 1:22 PM
To: 'OIC-OSD@...'; 'iotivity-dev@...'
Cc: 'Brian Warner (brian.warner@...)'
Subject: Re: [OIC-OSD] Moving 01.org to IoTivity.org

To all,

The transition to the GIT repositories at iotivity.org is complete. Please update your local repository references to the new repository.

The repositories at 01.org are still live but are marked read-only and you will not be able to push changesets to that repository any longer.
The build machine at the Linux Foundation needs some additional configuration for unit testing. This is causing continuous integration to report failures. We intend to close this gap as quickly as possible on Monday morning ET. We are sorry for the inconvenience.
Any pending reviews at 01.org will have to be resubmitted to iotivity.org. We are in the process of moving a couple of the pending reviews that we know are important. If we do not move yours and you need help let us know. Please note, that resubmitting drops the existing comments and the list of requested reviewers.

We have tagged the following branches as 0.9.0 release candidates on iotivity.org:
- Master branch: 0.9.0-RC1
- Connectivity Abstraction branch: 0.9.0-CA-RC1
- Control Manager branch: 0.9.0-CM-RC1
- Android Port M2 branch: <untagged>

At this point, I am asking maintainers to hold new feature patches and prioritize fixes as we pull these branches into a single release.

I would like to send thanks to June Yong, Uze Choi and Sudarshan Prasad for their around the clock (and world) assistance and especially Bill Dieter for his GIT planning and heavy lifting.

Pat Lankswert
DCTG Chair and Maintainer
_______________________________________________
OIC-OSD mailing list
OIC-OSD@...
https://lists.01.org/mailman/listinfo/oic-osd


Re: Moving 01.org to IoTivity.org

Dieter, William R <william.r.dieter@...>
 

I should also add, thanks to the Linux Foundation support team for helping get everything set up and fast response on the last minute issues.

Bill.

-----Original Message-----
From: iotivity-dev-bounces@... [mailto:iotivity-dev-bounces@...] On Behalf Of Dieter, William R
Sent: Sunday, December 21, 2014 3:54 PM
To: Lankswert, Patrick; 'OIC-OSD@...'; 'iotivity-dev@...'
Cc: 'Brian Warner (brian.warner@...)'
Subject: Re: [dev] Moving 01.org to IoTivity.org

Here is the current status of the iotivity.org infrastructure:

Item URL Status
------- ---------------- -------------
Web www.iotivity.org Up (access controlled with htaccess)
Wiki wiki.iotivity.org Up (access controlled via IP whitelist for OIC member companies)
Git/Gerrit gerrit.iotivity.org Up (IP whitelist)
Jenkins build.iotivity.org Up (IP whitelist)
Mailing list lists.iotivity.org Up (open to the whole world)
Jira jira.iotivity.org Up (for several weeks)

[ ... lots of stuff deleted ... ]


Out of the office

Dieter, William R <william.r.dieter@...>
 

I will be out of the office through 04 Jan 2015.  Email responses will be delayed, and I may not respond before I return to email that is not marked urgent.

 

If something important comes up, I will respond as quickly as possible, but please also copy Pat and Jaideep.  They will be able to handle git/gerrit related issues (and probably any other issues) that may arise and may be able to respond more quickly.

 

Happy Holidays,

Bill.


Re: [OIC-OSD] Moving 01.org to IoTivity.org

Thiago Macieira
 

No, -u is correct.

Your version of Git is old. Please consider upgrading.

On Monday 22 December 2014 01:22:53 오정현 wrote:
I have a question to ask about the "Git Command". When I tried the step
describe below...
git remote rename origin oic01
git remote add origin
ssh://<username>@gerrit.iotivity.org:29418/iotivity --> git branch -u
origin/master master
I faced an error message & that is.. "error : unknown switch 'u'".
Did you originaly mean by using 'm' instead of 'u' ???
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center


Re: [OIC-OSD] Iotivity Dec 20th Release

Zhang, Caiwen <caiwen.zhang@...>
 

Hi Kishen,

Thanks for pointing out this. I have submitted a patch for it.

https://gerrit.iotivity.org/gerrit/#/c/10/


Hi All,

There is a script (auto_build.sh) in the root directory of the source code. It will run all generic building cases automatically.
Please make sure all the cases are passed before submit any change.

Following is the usage of this script:

To build:
$ auto_build.sh <path-to-android-ndk> <path-to-arduino-home>
To clean:
$ auto_build.sh -c

You can also find above information in Readme.scons.txt (it is in the root directory of the source code)

Thanks,
Caiwen

-----Original Message-----
From: OIC-OSD [mailto:oic-osd-bounces@...] On Behalf Of Maloor,
Kishen
Sent: Monday, December 22, 2014 9:27 AM
To: Prasad, Sudarshan; OIC-OSD@...; iotivity-dev@...
Subject: Re: [OIC-OSD] Iotivity Dec 20th Release

It appears that the latest build up on Iotivity is broken.
The error is with cpluff:
In file included from
service/protocol-plugin/lib/cpluff/libcpluff/context.c:34:0:
service/protocol-plugin/lib/cpluff/libcpluff/cpluff.h:41:23: fatal error:
cpluffdef.h: No such file or directory compilation terminated.

I was able to fix it locally by adding:
cpluff_env.AppendUnique(CPPPATH = ['./libcpluff']) to
service/protocol-plugin/lib/cpluff/SConscript

-Kishen.

From: <Prasad>, Sudarshan
<sudarshan.prasad@...<mailto:sudarshan.prasad@...>>
Date: Sunday, December 21, 2014 at 4:36 PM
To: "OIC-OSD@...<mailto:OIC-OSD@...>"
<OIC-OSD@...<mailto:OIC-OSD@...>>,
"iotivity-dev@...<mailto:iotivity-dev@...>"
<iotivity-dev@...<mailto:iotivity-dev@...>>
Subject: [OIC-OSD] Iotivity Dec 20th Release

All,

Dec 20th release of Iotivity is available in new repositories at iotivity.org.

Commit id for master branch for Dec 20th release is:
35175a4c63b1ea76d5c0f5fb4c9e9bf1437c0290.
Corresponding release notes are available in
iotivity/resource/releaseNotes/Dec20th2014.txt.

Please refer to www.iotivity.org<http://www.iotivity.org> for information
on setting up GIT, Gerrit, and cloning code etc. from the new repository.

Thanks,
Sudarshan Prasad

_______________________________________________
OIC-OSD mailing list
OIC-OSD@...
https://lists.01.org/mailman/listinfo/oic-osd


Re: [OIC-OSD] Iotivity Dec 20th Release

최우제 (Uze Choi)
 

Hi Kishen,

From Our site, everything build well, after Heesung's commit on the last
Sat(KST).
I'm not sure which build error happen from yours.
Could you explain little bit more detail, which code you checked?

BR, Uze Choi

-----Original Message-----
From: OIC-OSD [mailto:oic-osd-bounces@...] On Behalf Of Maloor,
Kishen
Sent: Monday, December 22, 2014 10:27 AM
To: Prasad, Sudarshan; OIC-OSD@...; iotivity-dev@...
Subject: Re: [OIC-OSD] Iotivity Dec 20th Release

It appears that the latest build up on Iotivity is broken.
The error is with cpluff:
In file included from service/protocol-
plugin/lib/cpluff/libcpluff/context.c:34:0:
service/protocol-plugin/lib/cpluff/libcpluff/cpluff.h:41:23: fatal error:
cpluffdef.h: No such file or directory compilation terminated.

I was able to fix it locally by adding:
cpluff_env.AppendUnique(CPPPATH = ['./libcpluff']) to service/protocol-
plugin/lib/cpluff/SConscript

-Kishen.

From: <Prasad>, Sudarshan
<sudarshan.prasad@...<mailto:sudarshan.prasad@...>>
Date: Sunday, December 21, 2014 at 4:36 PM
To: "OIC-OSD@...<mailto:OIC-OSD@...>" <OIC-
OSD@...<mailto:OIC-OSD@...>>, "iotivity-
dev@...<mailto:iotivity-dev@...>" <iotivity-
dev@...<mailto:iotivity-dev@...>>
Subject: [OIC-OSD] Iotivity Dec 20th Release

All,

Dec 20th release of Iotivity is available in new repositories at
iotivity.org.

Commit id for master branch for Dec 20th release is:
35175a4c63b1ea76d5c0f5fb4c9e9bf1437c0290.
Corresponding release notes are available in
iotivity/resource/releaseNotes/Dec20th2014.txt.

Please refer to www.iotivity.org<http://www.iotivity.org> for information
on setting up GIT, Gerrit, and cloning code etc. from the new repository.

Thanks,
Sudarshan Prasad

_______________________________________________
OIC-OSD mailing list
OIC-OSD@...
https://lists.01.org/mailman/listinfo/oic-osd


Re: Moving 01.org to IoTivity.org

Lankswert, Patrick <patrick.lankswert@...>
 

Bill,

Let me echo that. The folks at LF have been amazing to work with.

Pat

-----Original Message-----
From: Dieter, William R
Sent: Sunday, December 21, 2014 3:57 PM
To: Dieter, William R; Lankswert, Patrick; 'OIC-OSD@...'; 'iotivity-dev@...'
Cc: 'Brian Warner (brian.warner@...)'
Subject: RE: Moving 01.org to IoTivity.org

I should also add, thanks to the Linux Foundation support team for helping get everything set up and fast response on the last minute issues.

Bill.

-----Original Message-----
From: iotivity-dev-bounces@... [mailto:iotivity-dev-bounces@...] On Behalf Of Dieter, William R
Sent: Sunday, December 21, 2014 3:54 PM
To: Lankswert, Patrick; 'OIC-OSD@...'; 'iotivity-dev@...'
Cc: 'Brian Warner (brian.warner@...)'
Subject: Re: [dev] Moving 01.org to IoTivity.org

Here is the current status of the iotivity.org infrastructure:

Item URL Status
------- ---------------- -------------
Web www.iotivity.org Up (access controlled with htaccess)
Wiki wiki.iotivity.org Up (access controlled via IP whitelist for OIC member companies)
Git/Gerrit gerrit.iotivity.org Up (IP whitelist)
Jenkins build.iotivity.org Up (IP whitelist)
Mailing list lists.iotivity.org Up (open to the whole world)
Jira jira.iotivity.org Up (for several weeks)

[ ... lots of stuff deleted ... ]


Re: [OIC-OSD] Moving 01.org to IoTivity.org

Lankswert, Patrick <patrick.lankswert@...>
 

June,

All of the branches have been tagged and I can create release branches at your leisure, but there is still a lot of clean up that needs to be done. There is not enough time to vet and merge the three (four?) branches into one branch by this time frame.

My current plan is:
- Finish bringing up the iotivity build machines.
I would like this completed for several of the main projects
(resources and some of the services) today.
- Start the merge process for one of the branches.
This requires review and validation that it does not break existing functionality.

In the meantime, I am receiving and reviewing patch commits for fixes.
I have seen several just this morning.

I expect this clean up to continue through the end of the year.
I am happy to put a tag on any intermediate version for release purposes,
but I would prefer that we save the official 0.9.0 tag for the snapshot that provides
the best developer experience.

Pat

From: 양준용 [mailto:juney@...]
Sent: Sunday, December 21, 2014 9:26 PM
To: Dieter, William R; Lankswert, Patrick; 'OIC-OSD@...'; 'iotivity-dev@...'
Cc: 'Brian Warner (brian.warner@...)'
Subject: Re: Re: [OIC-OSD] Moving 01.org to IoTivity.org

Pat, William,
 
Thank you for your hard work indeed.
BTW, We are supposed to freeze release branch at 12/22 08:00 AM, PST, aren't we?
Do you perhaps have any more additional schedule?
 
Regards
June
 
June Yong Young

Principal Engineer
Web & Convergence Team, Software R&D Center 
Samsung Electronics Co.,Ltd.

T: +82-31-301-6107, M: +82-10-9530-6107
E-mail :juney@...
 
------- Original Message -------
Sender : Dieter, William R<william.r.dieter@...>
Date : 2014-12-22 05:56 (GMT+09:00)
Title : Re: [OIC-OSD] Moving 01.org to IoTivity.org
 
I should also add, thanks to the Linux Foundation support team for helping get everything set up and fast response on the last minute issues.

Bill.

-----Original Message-----
From: iotivity-dev-bounces@... [mailto:iotivity-dev-bounces@...] On Behalf Of Dieter, William R
Sent: Sunday, December 21, 2014 3:54 PM
To: Lankswert, Patrick; 'OIC-OSD@...'; 'iotivity-dev@...'
Cc: 'Brian Warner (brian.warner@...)'
Subject: Re: [dev] Moving 01.org to IoTivity.org

Here is the current status of the iotivity.org infrastructure:

Item URL Status
------- ---------------- -------------
Web www.iotivity.org Up (access controlled with htaccess)
Wiki wiki.iotivity.org Up (access controlled via IP whitelist for OIC member companies)
Git/Gerrit gerrit.iotivity.org Up (IP whitelist)
Jenkins build.iotivity.org Up (IP whitelist)
Mailing list lists.iotivity.org Up (open to the whole world)
Jira jira.iotivity.org Up (for several weeks)

[ ... lots of stuff deleted ... ]
_______________________________________________
OIC-OSD mailing list
OIC-OSD@...
https://lists.01.org/mailman/listinfo/oic-osd


Re: M1 on IoTivity

Dieter, William R <william.r.dieter@...>
 

+ iotivity-dev

 

From: OIC-OSD [mailto:oic-osd-bounces@...] On Behalf Of Light, John J
Sent: Monday, December 22, 2014 2:12 PM
To: 'OIC-OSD@...'
Subject: [OIC-OSD] M1 on IoTivity

 

I cloned iotivity.  When I run doxygen on docs and go to docs/html/index.html, I am told it is M1 Release (at the top of the page).  OTOH, it seems to be the M2 documentation.

 

John Light

OTC CSD OIC Development

 


Re: [OIC-OSD] Moving 01.org to IoTivity.org

Dieter, William R <william.r.dieter@...>
 

Jay,

You might have an older version of git.  The –u option was introduced in git 1.8.0.  This stackoverflow answer should help if you are using git 1.7.0:

http://stackoverflow.com/questions/520650/make-an-existing-git-branch-track-a-remote-branch

Thanks,
Bill.

 

From: 오정현 [mailto:junghyun.oh@...]

Sent: Sunday, December 21, 2014 8:23 PM
To: Dieter, William R; Lankswert, Patrick; 'OIC-OSD@...'; 'iotivity-dev@...'
Cc: 'Brian Warner (brian.warner@...)'
Subject: Re: Re: [OIC-OSD] Moving 01.org to IoTivity.org

 

I have a question to ask about the "Git Command". When I tried the step describe below...

 

    git remote rename origin oic01
    git remote add origin ssh://<username>@gerrit.iotivity.org:29418/iotivity
--> git branch -u origin/master master

I faced an error message & that is.. "error : unknown switch 'u'".

Did you originaly mean by using 'm' instead of 'u' ???

 

Thank you.

Jay.

 

------- Original Message -------

Sender : Dieter, William R<william.r.dieter@...>

Date : 2014-12-22 05:54 (GMT+09:00)

Title : Re: [OIC-OSD] Moving 01.org to IoTivity.org

 

Here is the current status of the iotivity.org infrastructure:

Item URL Status
------- ---------------- -------------
Web www.iotivity.org Up (access controlled with htaccess)
Wiki wiki.iotivity.org Up (access controlled via IP whitelist for OIC member companies)
Git/Gerrit gerrit.iotivity.org Up (IP whitelist)
Jenkins build.iotivity.org Up (IP whitelist)
Mailing list lists.iotivity.org Up (open to the whole world)
Jira jira.iotivity.org Up (for several weeks)

As a reminder, please update your git remotes to point to iotivity.org:

    git remote rename origin oic01
    git remote add origin ssh://@gerrit.iotivity.org:29418/iotivity
    git branch -u origin/master master

Where is your Linux Foundation ID.  Please repeat the "git branch -u" command for each branch that you use, replacing "master" with the branch name (e.g., "git branch -u origin/connectivity-abstraction connectivity-abstraction).

If you had a pending commit in oic-review.01.org, the fastest way to get it moved to iotivity.org is to check out the commit and do

    git push origin HEAD:refs/for/

where is the branch to which you would like push.  Assuming you have updated your remotes, your commit will show up on gerrit.iotivity.org, and can be reviewed as usual.

Verification and Integration builds seem to be working on the build machine using the makefile build process.    I apologize for the several build notice emails some of you may have received.  Only one commit has been through the verification and integration build process, so there may be additional issues that will not appear until more commits are made.  If you run into problems, please send email to iotivity-dev@....  We were not able to get scons to build locally using the directions in the README and did not have time to debug the issue.  We will be working on the transition to scons as soon as possible.

Build verification works a little differently than on 01.org.  On 01.org, the build machine made a +1 or -1 review, just like human reviewers, based on build results.  On iotivity.org, the build machine adds its +1 (or -1) to a separate "Verified" field that is independent of the Code Review provided by people.

Please send all new mailing list traffic to the iotivity-dev mailing list.

Thanks,
Bill.

-----Original Message-----
From: OIC-OSD [mailto:oic-osd-bounces@...] On Behalf Of Lankswert, Patrick
Sent: Sunday, December 21, 2014 1:22 PM
To: 'OIC-OSD@...'; 'iotivity-dev@...'
Cc: 'Brian Warner (brian.warner@...)'
Subject: Re: [OIC-OSD] Moving 01.org to IoTivity.org

To all,

The transition to the GIT repositories at iotivity.org is complete. Please update your local repository references to the new repository.

The repositories at 01.org are still live but are marked read-only and you will not be able to push changesets to that repository any longer.
The build machine at the Linux Foundation needs some additional configuration for unit testing. This is causing continuous integration to report failures. We intend to close this gap as quickly as possible on Monday morning ET. We are sorry for the inconvenience.
Any pending reviews at 01.org will have to be resubmitted to iotivity.org. We are in the process of moving a couple of the pending reviews that we know are important. If we do not move yours and you need help let us know. Please note, that resubmitting drops the existing comments and the list of requested reviewers.

We have tagged the following branches as 0.9.0 release candidates on iotivity.org:
- Master branch: 0.9.0-RC1
- Connectivity Abstraction branch: 0.9.0-CA-RC1
- Control Manager branch: 0.9.0-CM-RC1
- Android Port M2 branch:

At this point, I am asking maintainers to hold new feature patches and prioritize fixes as we pull these branches into a single release.

I would like to send thanks to June Yong, Uze Choi and Sudarshan Prasad for their around the clock (and world) assistance and especially Bill Dieter for his GIT planning and heavy lifting.

Pat Lankswert
DCTG Chair and Maintainer
_______________________________________________
OIC-OSD mailing list
OIC-OSD@...
https://lists.01.org/mailman/listinfo/oic-osd
_______________________________________________
OIC-OSD mailing list
OIC-OSD@...
https://lists.01.org/mailman/listinfo/oic-osd

 

 

Jung-hyun Oh.  

Advanced Convergence Lab.  | SW R&D Center | SAMSUNG ELECTRONICS CO.,LTD

Mobile +82-10-9890-6731 | Beyond your imagination, Always

 

 


Re: [OIC-OSD] Iotivity Dec 20th Release

Light, John J <john.j.light@...>
 

When I build IoTivity, I get

service/protocol-plugin/lib/cpluff/libcpluff/ploader.c:35:19: fatal error: expat.h: No such file or directory
#include <expat.h>
^
compilation terminated.

This is similar to earlier cpluff problem, but different.

Please advise. I can't test the review changes without a working M2.

John Light
OTC CSD OIC Development

-----Original Message-----
From: OIC-OSD [mailto:oic-osd-bounces@...] On Behalf Of Maloor, Kishen
Sent: Monday, December 22, 2014 12:26 PM
To: 최우제(Uze Choi); Prasad, Sudarshan; OIC-OSD@...; iotivity-dev@...
Subject: Re: [OIC-OSD] Iotivity Dec 20th Release

Uze,
Please refer to my e-mail below for the location of the error.
The code was from master/HEAD of the iotivity repo. I built by running “scons TARGET_OS=linux TARGET_ARCH=x86 RELEASE=1”.
Caiwen’s patch addresses the problem, so this is no longer an issue.
-Kishen.

On 12/21/14, 11:37 PM, "최우제(Uze Choi)" <uzchoi@...> wrote:

Hi Kishen,

From Our site, everything build well, after Heesung's commit on the
last Sat(KST).
I'm not sure which build error happen from yours.
Could you explain little bit more detail, which code you checked?

BR, Uze Choi
-----Original Message-----
From: OIC-OSD [mailto:oic-osd-bounces@...] On Behalf Of
Maloor, Kishen
Sent: Monday, December 22, 2014 10:27 AM
To: Prasad, Sudarshan; OIC-OSD@...;
iotivity-dev@...
Subject: Re: [OIC-OSD] Iotivity Dec 20th Release

It appears that the latest build up on Iotivity is broken.
The error is with cpluff:
In file included from service/protocol-
plugin/lib/cpluff/libcpluff/context.c:34:0:
service/protocol-plugin/lib/cpluff/libcpluff/cpluff.h:41:23: fatal error:
cpluffdef.h: No such file or directory compilation terminated.

I was able to fix it locally by adding:
cpluff_env.AppendUnique(CPPPATH = ['./libcpluff']) to service/protocol-
plugin/lib/cpluff/SConscript

-Kishen.

From: <Prasad>, Sudarshan
<sudarshan.prasad@...<mailto:sudarshan.prasad@...>>
Date: Sunday, December 21, 2014 at 4:36 PM
To: "OIC-OSD@...<mailto:OIC-OSD@...>" <OIC-
OSD@...<mailto:OIC-OSD@...>>, "iotivity-
dev@...<mailto:iotivity-dev@...>"
<iotivity-
dev@...<mailto:iotivity-dev@...>>
Subject: [OIC-OSD] Iotivity Dec 20th Release

All,

Dec 20th release of Iotivity is available in new repositories at
iotivity.org.

Commit id for master branch for Dec 20th release is:
35175a4c63b1ea76d5c0f5fb4c9e9bf1437c0290.
Corresponding release notes are available in
iotivity/resource/releaseNotes/Dec20th2014.txt.

Please refer to www.iotivity.org<http://www.iotivity.org> for
information on setting up GIT, Gerrit, and cloning code etc. from the new repository.

Thanks,
Sudarshan Prasad

_______________________________________________
OIC-OSD mailing list
OIC-OSD@...
https://lists.01.org/mailman/listinfo/oic-osd
_______________________________________________
OIC-OSD mailing list
OIC-OSD@...
https://lists.01.org/mailman/listinfo/oic-osd