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: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] 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
