Hi Mats On 17/01/17 16:32, Mats Wichmann wrote: > Based on what I thought was the plan - to do an IoTivity 2.0 fairly soon > (see wiki, is it out of date?), Well I am not into planning but it would be nice to have all (or most) 1.2-rel merged into master before forking it at least the cloud module which have been not fully merged, What do you think of this ?
> I'm surprised at the number of commits > still going into 1.2. probably requirements for projects using 1.2 > 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. There's even been some ongoing low-level chatter It would be nice to release a 1.2.2 too. > wondering if all the 1.2 commits are actually making it into master. I am tracking this. I tried to push back changes from 1.2-rel branches Because there are dependencies between, merging is taking time, but maintainers are active on this task. I will try again to rebase 1.2-rel on master and push the whole serie, next weekend(s). But there are about 30 patches that need to be ported or dropped, please can you check the list "Conflicts to solve:" at : https://wiki.iotivity.org/1.2-rel and eventually comment their states in gerrit But the priority is to review/merge those pending "mergeback" changes: https://gerrit.iotivity.org/gerrit/#/q/status:open+project:iotivity+topic:mergeback+is:mergeable+AND++NOT+label:Code-Review%253D-1+AND++NOT+label:Code-Review%253D-2++AND+NOT+label:Verified%253D-1 Thank you -- mailto:philippe.coval at osg.samsung.com gpg:0x467094BC https://blogs.s-osg.org/author/pcoval/
