My merges of 'feature/16.10.02' into RB16.10 are not yet merged to RB16.10 branch (review is pending in Gerrit), once it happens test builds can be done on RB16.10 branch.
On Tue, Jun 20, 2017 at 6:07 PM, Hertel, Carrie Lynn < carrie.her...@oregonstate.edu> wrote: > 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 <(541)%20737-6012> > > cass.oregonstate.edu > > > > *From:* Krystian Zlomek [mailto:kzlo...@affinegy.com] > *Sent:* Tuesday, June 20, 2017 8:04 AM > *To:* Josh Spain <jsp...@affinegy.com> > *Cc:* C.J. Collier <cjcoll...@linuxfoundation.org>; Karol Matuszkiewicz < > kmatuszkiew...@affinegy.com>; Hertel, Carrie Lynn < > carrie.her...@oregonstate.edu>; Paul Sigurdson <psigurd...@affinegy.com>; > alljoyn-core@lists.alljoyn.org; Jorge Martinez <jmarti...@affinegy.com> > > *Subject:* Re: 16.10.01 is Ready! > > > > Hi, > > > > I've just submitted merge of 'feature/16.10.02' into RB16.10 > <https://git.allseenalliance.org/gerrit/11807>: > > > > 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. > > > > > > Note that there are 2 commits submitted to 'feature/16.10.02 > <https://git.allseenalliance.org/gerrit/11807> which could not be merged > now: > > https://git.allseenalliance.org/gerrit/#/c/11781/ > > https://git.allseenalliance.org/gerrit/#/c/11797/ > > > > Those commits should be updated and resubmitted to RB16.10 > <https://git.allseenalliance.org/gerrit/11807>. > > > > Thanks, > > Krystian > > > > On Mon, Jun 19, 2017 at 8:20 PM, Josh Spain <jsp...@affinegy.com> wrote: > > Thanks CJ! > > > > *@Carrie*: the merge from feature/16.10.02 to RB16.10 is in the pipeline. > I'm hoping we can get the merge completed this afternoon. > > > > *@Team*: the win7 verification build failed. It appears to have hung on > KeyStoreTest.concurrent_access_single_keystore_inmemory > <https://build.allseenalliance.org/ci/job/win7-rel-bvt/1712/console>. I > haven't been able to verify that this is a normal intermittent failure > rather than something new. Can anyone on the team confirm? > > > > The merge is here: > > https://git.allseenalliance.org/gerrit/#/c/11805/ > > > > Thanks, > > Josh > > > > On Mon, Jun 19, 2017 at 11:56 AM, C.J. Collier < > cjcoll...@linuxfoundation.org> wrote: > > Done. > > > > On Mon, Jun 19, 2017 at 8:27 AM, Josh Spain <jsp...@affinegy.com> wrote: > > 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 < > cjcoll...@linuxfoundation.org> wrote: > > Commits tagged! > > > > On Thu, May 18, 2017 at 9:30 AM, Josh Spain <jsp...@affinegy.com> wrote: > > 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 > <https://cgit.allseenalliance.org/core/alljoyn.git/tag/?h=v16.10.01-rc0>) > > *ajtcl.git:* https://cgit.allseenalliance.org/core/ > ajtcl.git/commit/?h=refs/heads/RB16.10&id=496c41779320e015e059f685b198e6 > dac3f5ea2b > > > (tagged with: v16.10.01-rc0 > <https://cgit.allseenalliance.org/core/ajtcl.git/tag/?h=v16.10.01-rc0> > > ) > > > > Thanks, > > Josh > > > > On Wed, May 17, 2017 at 2:25 AM, Karol Matuszkiewicz < > kmatuszkiew...@affinegy.com> wrote: > > 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 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 <%28541%29%20737-6012> > > cass.oregonstate.edu > > > > *From:* Paul Sigurdson [mailto:psigurd...@affinegy.com] > *Sent:* Tuesday, May 16, 2017 11:22 AM > *To:* Josh Spain > *Cc:* Krystian Zlomek; alljoyn-core@lists.alljoyn.org; Hertel, Carrie > Lynn; Jorge Martinez; Karol Matuszkiewicz > *Subject:* Re: 16.10.01 is Ready! > > > > FYI… > > > > These two JIRA issues (that are merged into 16.10.01), are still marked > with status “in test”. > > > > https://jira.allseenalliance.org/browse/ASACORE-3032 > > https://jira.allseenalliance.org/browse/ASACORE-3528 > > > > -Paul > > > > On May 16, 2017, at 12:18 PM, Paul Sigurdson <psigurd...@affinegy.com> > wrote: > > > > Looks good. > > > > On May 16, 2017, at 11:41 AM, Josh Spain <jsp...@affinegy.com> wrote: > > > > *Copying the Core WG mailing list* > > > > I need responses from Paul, Jorge, and Karol, then we can make the tag. > > > > Thanks, > > Josh > > > > On Thu, May 11, 2017 at 12:37 PM, Krystian Zlomek <kzlo...@affinegy.com> > wrote: > > I meant that proposed commits for tag v16.10.01 look correct to me. > > Thanks, > Krystian > > > > On Thu, May 11, 2017 at 7:36 PM, Krystian Zlomek <kzlo...@affinegy.com> > wrote: > > > > Proposed tags look correct to me. > > > > Thanks, > > Krystian > > > > On Thu, May 11, 2017 at 7:00 PM, Hertel, Carrie Lynn <carrie.hertel@ > oregonstate.edu> wrote: > > QA is complete! > > > > *CARRIE HERTEL, PMP,* CASS Director – SDG, TL, IoT > > Oregon State University | EECS/CASS | 541-737-6012 <%28541%29%20737-6012> > > cass.oregonstate.edu > > > > *From:* Josh Spain [mailto:jsp...@affinegy.com] > *Sent:* Thursday, May 11, 2017 9:11 AM > *To:* Hertel, Carrie Lynn <carrie.her...@oregonstate.edu>; Krystian > Zlomek <kzlo...@affinegy.com>; Paul Sigurdson <psigurd...@affinegy.com>; > Jorge Martinez <jmarti...@affinegy.com>; Karol Matuszkiewicz < > kmatuszkiew...@affinegy.com> > *Subject:* 16.10.01 is Ready! > > > > AllJoyn 16.10.01 Core Team: > > All of the changes are merged for the 16.10.01 release, and release > candidate builds have been generated. I confirm that development is > complete and no further commits are in the pipeline. > > Please confirm: > > - *Committers*: that the v16.10.01 tag should be placed on the commits > identified below > - *Carrie*: that QA is complete > > The commit IDs proposed for the v16.10.01 tag are: > > > > *alljoyn.git:* https://cgit.allseenalliance.org/core/ > alljoyn.git/commit/?id=2b25f758f3aa576970e4023f661dfead2da3c8f9 > (tagged with: v16.10.01-rc1 > <https://cgit.allseenalliance.org/core/alljoyn.git/tag/?h=v16.10.01-rc1>) > > *ajtcl.git:* https://cgit.allseenalliance.org/core/ > ajtcl.git/commit/?h=refs/heads/RB16.10&id=496c41779320e015e059f685b198e6 > dac3f5ea2b > (tagged with: v16.10.01-rc1 > <https://cgit.allseenalliance.org/core/ajtcl.git/tag/?h=v16.10.01-rc1>) > > -Josh > > > > > > > > > > > > > > > > > > >
_______________________________________________ Alljoyn-core mailing list Alljoyn-core@lists.alljoyn.org https://lists.alljoyn.org/mailman/listinfo/alljoyn-core
