Hi Uze, et al., I've uploaded a patchset to create 1.3-rel merge verification jobs [1] and would appreciate any feedback.
Similar to the 1.2-rel and 1.1-rel branches, these jobs are to ensure the 1.3-rel branch stays stable during the release process. All code before being merged in will still be verified by Jenkins[2]. Currently these jobs are copies of the 1.2-rel merge jobs, and I will update the patchset today to include the other jobs from master. Please comment on the patchset and let me know if there should be any changes to the proposed jobs. Thanks! Regards, Trevor Bramwell [1] https://gerrit.iotivity.org/gerrit/#/c/19137/ [2] https://build.iotivity.org/ci/view/iotivity/ On Mon, Apr 17, 2017 at 04:00:19PM +0900, ??? (Uze Choi) wrote: > 1.3.0-RC1 is tagged on 1.3-rel branch. > > > > BR, Uze Choi > > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-bounces > at lists.iotivity.org] On Behalf Of ??? (Uze Choi) > Sent: Friday, April 14, 2017 4:19 PM > To: iotivity-maintainers at lists.iotivity.org > Cc: iotivity-dev at lists.iotivity.org > Subject: [dev] [RC1 Taggable check] RE: 1.3-rel Branch out/QA start request. > > > > Hi Each maintainer, > > I?d like to make a RC1 tag on 1.3-rel. > > If have the issue for test start for each module, please correct&merge them > and make the branch code working well. > > And let me know to hold on tag prior to merging launched. > > BR, Uze Choi > > From: Bell, Richard S [mailto:richard.s.bell at intel.com] > Sent: Wednesday, April 12, 2017 6:16 AM > To: uzchoi at samsung.com; Kevin Kane; Mats Wichmann; iotivity-dev at > lists.iotivity.org > Subject: RE: [dev] 1.3-rel Branch out/QA start request. > > > > Uze, > > I notice that you had created the 1.3-rel branch but no tag. > > Will there be a tag? > > > > I have created the 1.3-rel branch for iotivity-upnp-bridge > (https://gerrit.iotivity.org/gerrit/#/admin/projects/iotivity-upnp-bridge,branches) > > I will add the a similar tag when put in iotivity. > > We will test 1.3-rel branch for iotivity-upnp-bridge with 1.3-rel branch > iotivity. > > > > Thanks, > > -Rick > > > > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-bounces > at lists.iotivity.org] On Behalf Of ??? > Sent: Monday, April 10, 2017 3:50 PM > To: Kevin Kane <kkane at microsoft.com>; Mats Wichmann <mats at wichmann.us>; > iotivity-dev at lists.iotivity.org > Subject: Re: [dev] 1.3-rel Branch out/QA start request. > > > > Definitely. > > Please mergeback into master after work on 1.3-rel if not release branch > specific. > > BR Uze Choi > > > > --------- Original Message --------- > Sender : Kevin Kane <kkane at microsoft.com> > Date : 2017-04-11 07:31 (GMT+9) > Title : RE: RE: [dev] 1.3-rel Branch out/QA start request. > > For changes that are already pending, that sounds fine, especially since the > branches haven?t yet diverged at all. But from this point forward, for any > new changes, let?s submit directly to 1.3-rel and then have a regular merge > cadence. > > > > From: ??? [mailto:uzchoi at samsung.com] > Sent: Monday, April 10, 2017 3:24 PM > To: Kevin Kane <kkane at microsoft.com>; Mats Wichmann <mats at wichmann.us>; > iotivity-dev at lists.iotivity.org > Subject: RE: RE: [dev] 1.3-rel Branch out/QA start request. > > > > Hi Kevin, > > Thank you for your suggestion. > > It will be good to strictly follow the release branch merging policy. > > However for the better efficiency, let's accept currently pending commits > merged into master branch first and cherrypick in to 1.3-rel as a next step. > > BR Uze Choi > > > > --------- Original Message --------- > Sender : Kevin Kane <kkane at microsoft.com> > Date : 2017-04-11 06:14 (GMT+9) > Title : RE: [dev] 1.3-rel Branch out/QA start request. > > It'd be better for any 1.3 changes/bug fixes to be committed directly to > 1.3-rel, and then 1.3-rel should be merged regularly into master to pick > those changes up for the future. I'd suggest any pending changes on master > that should be in 1.3 be abandoned and resubmitted to 1.3-rel. All the > cherry-picking that happened between 1.2-rel and master did not work well at > all. > > -----Original Message----- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-bounces > at lists.iotivity.org] On Behalf Of Mats Wichmann > Sent: Monday, April 10, 2017 1:50 PM > To: ??? (Uze Choi) <uzchoi at samsung.com>; iotivity-dev at lists.iotivity.org > Subject: Re: [dev] 1.3-rel Branch out/QA start request. > > On 04/10/2017 04:57 AM, ??? (Uze Choi) wrote: > > Hi All, > > > > > > > > 1.3-rel branch has been created. 1.3.0 Release period just started. > > > > There are approximately 70 change sets waiting merge on the master > > branches > > > > Except this patches, All code merge should have the release management Lead > > review +1 on the release branch. > > > So for owners of waiting changesets... how do we proceed? The small number I > have in the queue (five public) I would not consider release-critical, but > also letting master and 1.3-rel diverge is not wonderful, makes lots of work > later for someone - I'm remembering what Phil and others had to do to get > master back in sync with 1.2-rel. > > Advice please? > > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev > > <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev&data=02%7C01%7Ckkane%40microsoft.com%7C3a7057b259e34a700d8608d4805326b6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636274542026472282&sdata=kaW7CiPhNlVkyehkZTEnFkQMMNTJXNXUHlkjKaXuMWQ%3D&reserved=0> > > &data=02%7C01%7Ckkane%40microsoft.com%7C3a7057b259e34a700d8608d4805326b6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636274542026472282&sdata=kaW7CiPhNlVkyehkZTEnFkQMMNTJXNXUHlkjKaXuMWQ%3D&reserved=0 > > > > > > > > > > > > > <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=uzchoi&do=bWFpbElEPTIwMTcwNDEwMjI1MDAxZXBjbXMxcDc0NWFkNzAyODE2MThlOTBlMjU3YjJkOTJjYTIyYWRkYyZyZWNpcGllbnRBZGRyZXNzPWlvdGl2aXR5LWRldkBsaXN0cy5pb3Rpdml0eS5vcmc_> > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170420/313206ef/attachment.sig>
