Re: [Alljoyn-core] 16.10.01 is Ready!

I’m assuming this means the build isn’t ready to start testing just yet? I just want to make sure I’m not missing something. Thanks, Carrie CARRIE HERTEL, PMP, CASS Director – SDG, TL, IoT Oregon State University | EECS/CASS | 541-737-6012 cass.oregonstate.edu From: Krystian Zlomek

Re: [Alljoyn-core] 16.10.01 is Ready!

Hi, I've just submitted merge of 'feature/16.10.02' into RB16.10 : ajtcl:https://git.allseenalliance.org/gerrit/#/c/11809/ alljoyn: https://git.allseenalliance.org/gerrit/#/c/11807/ When Jenkins verifies those merges then I'll add reviewers.

Re: [Alljoyn-core] 16.10.01 is Ready!

All: the 16.10.01 review period is over, so we can begin merging 16.10.02 features with RB16.10 now. *@C.J.*, can you rename the v16.10.01-rc0 tag to v16.10.01? Thanks! Josh On Thu, May 18, 2017 at 1:32 PM, C.J. Collier wrote: > Commits tagged! > > On Thu, May

Re: [Alljoyn-core] 16.10.01 is Ready!

C.J., Please apply the following tags: *alljoyn.git:* https://cgit.allseenalliance.org/core/ alljoyn.git/commit/?id=2b25f758f3aa576970e4023f661dfead2da3c8f9 (tagged with: v16.10.01-rc0 ) *ajtcl.git:*

Re: [Alljoyn-core] 16.10.01 is Ready!

I confirm that the v16.10.01 tag should be placed on the given commits. Regards, Karol On Tue, May 16, 2017 at 8:34 PM, Hertel, Carrie Lynn < carrie.her...@oregonstate.edu> wrote: > I think both of these moved after we weren’t checking anymore and I didn’t > get flagged on them. I can have

Re: [Alljoyn-core] 16.10.01 is Ready!

I think both of these moved after we weren't checking anymore and I didn't get flagged on them. I can have someone at them today if that helps?? Thanks, Carrie CARRIE HERTEL, PMP, CASS Director - SDG, TL, IoT Oregon State University | EECS/CASS | 541-737-6012 cass.oregonstate.edu From: Paul