Re: [dev] [Iotivity-maintainers] request for 1.3-rel code freeze

[ABITHA S]

Title: Samsung Enterprise Portal mySingle

Dear Phil,   Post security issues are addressed, testing is in progress for confirming stability of the code. Below is the summary of present status.   1. Post RC5, we had few critical P1 issues raised in other modules which needed immediate attention and solving. Below Table details the issues reported and resolved post RC5 tagging   Issue key Summary Assignee Priority Status Found in Version Component/s Updated 1 IOT-2874 UDP over Wired Ethernet vs. WiFi testing results are inconsistent mkettrick P1 Resolved 1.3-rel Discovery/Connectivity 11/16/2017 16:48 2 IOT-2660 RD DELETE returns OC_STACK_RESOURCE_CHANGED, should return OC_STACK_RESOURCE_DELETED todd.malsbary P1 Resolved 1.3 Discovery/Connectivity 11/10/2017 0:52 3 IOT-2876 [CTT] A network problem occurs in Security. i.mushfiq P1 Resolved 1.3.1-RC4 Security 11/9/2017 5:54 4 IOT-2618 [CTT] [RI] GET response for '/introspection' resource now has 'href' property, which is invalid i.mushfiq P1 Resolved 1.3-rel SDK 11/8/2017 23:54 5 IOT-2877 CT1.7.8.11 - spurious results including handshake failure nathanheldtsheller P1 Resolved 1.5.26 CTT or other non-IoTivity component 11/8/2017 1:21 6 IOT-2852 1.7.4.5 - role cert test case failures nathanheldtsheller P1 Resolved CTT1.5.23 vs. IoTivity 1.3-rel 1502b2... CTT or other non-IoTivity component 11/8/2017 0:36 7 IOT-2856 The Default Interface for a multi-value "rt" Resource is oic.if.baseline i.mushfiq P1 Resolved 1.3-rel Sample Application 11/6/2017 5:34   2. CTT update for testing optional features are in progress and we are awaiting updates for WES and Batch interface which was due for 17th November and Delayed.  Also we have 2 P1 issues which requires update in CTT. details below.   Issue key Summary Assignee Priority Status Found in Version Component/s 1 IOT-1738 AllJoyn Bridge implementation todd.malsbary P1 Open 1.3-rel Alljoyn Bridge 2 IOT-2893 CTT's OIC server generates invalid response i.mushfiq P1 Reopened 1.3.1-RC5 CTT or other non-IoTivity component 3 IOT-2899 IoTivity blocking observe notification from links in collection when collection is observed using batch interface mkettrick P1 Open 1.3.1-RC5 CTT or other non-IoTivity component   Once CTT update is released and tested for optional features along with 2 pending P1 and working as expected, I will be making Final release candidate RC6, which will be tagged for 1.3.1.   Please let me know if any modifications are essential.   Regards, Abitha   --------- Original Message --------- Sender : Heldt-Sheller, Nathan <nathan.heldt-shel...@intel.com> Date : 2017-11-20 23:01 (GMT+5:30) Title : RE: [Iotivity-maintainers] [dev] request for 1.3-rel code freeze   Hi Phil,   This request from me for freeze is somewhat out of date at this time, because RC5 tag contains all needed security-related fixes for 1.3.1 final release.   I have noted that 1.3.1 final tag has not been created even though security fixes were done 2 weeks ago.  At this time, I am not sure what is happening in other IoTivity areas, but I *think* there are other fixes still ongoing, and there may be a RC6 tag at some point.  Abitha, Dwarka or Uze (all cc’d) may know more details.   I still think we should be focusing on master for all patches that are not required for CTT fix, but again, that is not my decision alone.  At the very least, I think all patches should undergo regression testing against CTT prior to merge, to make sure no new issues are introduced.   I have been doing this with any security patches, along with help from Antu. Thanks, Nathan       From: iotivity-maintainers-boun...@lists.iotivity.org [mailto:iotivity-maintainers-boun...@lists.iotivity.org] On Behalf Of Philippe Coval Sent: Monday, November 20, 2017 9:12 AM To: iotivity-dev@lists.iotivity.org; iotivity-maintain...@lists.iotivity.org Subject: Re: [Iotivity-maintainers] [dev] request for 1.3-rel code freeze   On 05/11/17 01:55, Heldt-Sheller, Nathan wrote: Hi folks, Hi everyone,   As we are just about to tag 1.3-rel RC5, good, I've tried to build on various system I am supporting, so far so good, but some may expect problem due to scons versions but it's not a blocker, and I will push most of my pending changes to on master first, and will keep you updated if interested, Don't hesitate to report bugs on tracker it's easier to track when things broke, and do fast bisection. I suggest that ONLY patches that fix certification-blocking issues be merged between now and when we have a 1.3.1 final tag done. So there is no RC6 planned ?   I’ve given a -2 review to many patches that look perfectly fine, along with a comment that I’ll remove the -2 as soon as RC5 is done (but I guess I meant to say, as soon as 1.3.1 is tagged).   Even very safe changes create a bit of instability and extra work, as all the devs and QA working on finalizing the release have to re-fetch and re-pull and re-build 1.3-rel.  Since we are already a few weeks behind schedule for 1.3.1 release, I hope everyone can hang on just a bit before we merge anything more to 1.3-rel.  There is a follow-on release planned immediately after 1.3.1, in order to incorporate other very important features, so these patches can go into that release (1.3.2?), too, before we move off of 1.3-rel and onto master for the next major version. For desired "safe changes" may I suggest to add the 'next' label, to make sure it in next version, and it will be noticed by downstream: https://gerrit.iotivity.org/gerrit/#/q/status:open+project:iotivity+topic:next   Obviously this isn’t my sole judgement call (it’s probably Uze’s or Abitha’s) but I’m suggesting this and hope we can agree. OK for me, I won't merge anything on 1.3-rel unless requested or hard blocking But for master is open for reviews, please have a look at: https://gerrit.iotivity.org/gerrit/#/c/22733/ and then those ones: https://gerrit.iotivity.org/gerrit/#/q/branch:master+status:open+project:iotivity+is:mergeable+AND++NOT+label:Code-Review%253D-1+AND++NOT+label:Code-Review%253D-2++AND+NOT+label:Verified%253D-1 Kind regards and good luck for the final fixes -- mailto:philippe.co...@osg.samsung.com gpg:0x467094BC https://blogs.s-osg.org/author/pcoval/     Thanks and Regards, Abitha.S

_______________________________________________
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev