Hi All, Let me answer for each topic.
[Release Plan] Each release requires lots of efforts including merge status verification, QA and so on. I'd like to spend the effort for specific purpose especially product planning friendly. For eaxmaple, Each release should have some reason as follows. - IoTivity 1.2.1 version has been released to secure the CTT 1.4 compliant version for '17 product shipping. - IoTivity 1.2.2 has been suggested by Microsoft for their product, but not yet officially requested. Let me ask it to Microsoft in this week ISG meeting. - IoTivity 2.0.0 version with OCF 1.0 certification beta version alignment for plugfest or product preparation. - IoTivity 2.1.0 version with OCF 1.1 certification version alignment for plugfest or product preparation. [1.2 branch] Based on 1.2 feature (more specifically 1.2.1 code), bug fix should be patched on 1.2-rel with master merge-back (or vice-versa). This merge back is maintainer responsibility. Currently Phil is helping and checking for missed items on master branch. Additional fix beyond these should be patched only into the master branch. However, currently patches are merged on 1.2-rel without this criteria or judgement or judgement is different from each project maintainer. Previously 1.2-rel merged was reviewed by me but not anymore after 1.2.1 release. If needed, assign the 1.2-rel branch manager and let them check merge is acceptable or not. BR, Uze Choi (Iotivity Release Function Lead) -----Original Message----- From: Heldt-Sheller, Nathan [mailto:[email protected]] Sent: Wednesday, January 18, 2017 10:38 AM To: Mats Wichmann; Philippe Coval; iotivity-dev at lists.iotivity.org; iotivity-maintainers at lists.iotivity.org Cc: 'Dwarkaprasad Dayama'; ???(Uze Choi) (uzchoi at samsung.com); Randeep Singh Subject: RE: [dev] Ongoing 1.2 development Thanks for bringing this up against Mats, Phil, I've been asking the same question... the Security features for 2.0 are being developed against Master where possible, but for the most part, the changes are still dependent on patches that haven't been cherry picked to Master. So we have continued new development on the 1.2-rel branch, which continues to create more cherry picking/merge work. We need the maintainers to make this a top priority to bring Master up to date with 1.2-rel, so that new development can be pushed to Master, or we're going to have a merge backlog and miss our release dates for IoTivity 2.0. Thanks, Nathan Heldt-Sheller OSWG Security TG Chair -----Original Message----- From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of Mats Wichmann Sent: Tuesday, January 17, 2017 8:27 AM To: Philippe Coval <philippe.coval at osg.samsung.com>; iotivity- dev at lists.iotivity.org; iotivity-maintainers at lists.iotivity.org Subject: Re: [dev] Ongoing 1.2 development On 01/17/2017 09:19 AM, Philippe Coval wrote: > Hi Mats >> If those are all classed as maintenance that's fine, but it's still >> been a little unexpected to see so much traffic after the release. > It would be nice to release a 1.2.2 too. I think that's what I was leading to, without ever getting to saying so: if there have been many changes to 1.2.1, it's hard for people basing their product work on 1.2.1 to keep track. Seems like we ought to be planning on 1.2.2 to roll up the changes, so there's a clean release. I know doing another release is a pain and consumes a fair bit of work, but how else to be reliably confident the changes get in the hands of the people using 1.2 branch? _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
