Ashok- Can you list these please? I can do my best to do a run-though. I'd prefer not to accept any of them individually, since a few of them seem to have interdependencies, so I'd like for all of them to be ready all at once.
Thanks, Erich On Wed, 2015-06-24 at 13:49 +0000, Lankswert, Patrick wrote: > Ashok, > > Excellent. Thanks! > > Pat > > > > From: ASHOKBABU CHANNA [mailto:ashok.channa at samsung.com] > Sent: Wednesday, June 24, 2015 12:41 AM > To: Lankswert, Patrick > Cc: iotivity-dev at lists.iotivity.org > Subject: Re: RE: New branch and design policies > > > > > Pat, > > Yes, all threading change sets are in available in gerrit. > > Ashok > > ------- Original Message ------- > > Sender : Lankswert, Patrick<patrick.lankswert at intel.com> > > Date : Jun 24, 2015 02:13 (GMT+09:00) > > Title : RE: New branch and design policies > > > > Ashok, > > One additional question: Are all of the threading change sets in > gerrit? > > I want to make sure that he code under review is gerrit is whole and > complete if I am going to accept it into master. > > Pat > > > > From: ASHOKBABU CHANNA [mailto:ashok.channa at samsung.com] > Sent: Tuesday, June 23, 2015 1:57 AM > To: Lankswert, Patrick > Cc: iotivity-dev at lists.iotivity.org > Subject: New branch and design policies > > > > > Dear Pat, > > > > Could you clarify on the new branch policy? > > > > 1) As far as we know, new features should be committed and reviewed in > new branches and only optimizations/bug fixes should go in master > branch directly. > > We are not sure why the optimization/fixes( single thread /multi > thread) are moved to new branch and IPV6 modifications such > ashttps://gerrit.iotivity.org/gerrit/#/c/1081/ are merged to master > mentioning it as high priority. > > Last 2 months, we resolved merge conflicts and expecting them to be > merged . But now all of a sudden Erich is requesting for merge them in > a new branch. > > 2) When we committed source , it?s been requested to make smaller > commits but now it?s been asked to make larger commit which is > impossible considering all platforms CA supports. > > And > > Design Policies: > > Some of the design decisions are taken internally without any > discussion in developer list or mentioning it in dc tg conference > calls which happens once in every two weeks. > > > > Here are the some comments in gerrit: > > Previous discussions on this are closed. > > Discussion was had, removed for good reason. > > https://gerrit.iotivity.org/gerrit/#/c/1081/42/resource/csdk/connectivity/api/cainterface.h > > Can we have the discussions open to theall developers instead of only > to internal members? > > > > > > > Regards, > > Ashok > > > > > > > > > > > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
