All, Carrie found a typo in the SC reelase notes, so I need to ask for signoff on SC again. I just merged the change, it is commit: 196ff5618b546f01004485fbbb1c41c5ff5ee74c the link is following: https://cgit.allseenalliance.org/core/alljoyn.git/commit/?h=RB16.10&id=196ff5618b546f01004485fbbb1c41c5ff5ee74c
Please confirm you are good with the change so we can drop the tags (once I get TSC clarity on what it should be) on that commit (rather than the previous) and the already approved ajtcl commit. From: Arvind Padole [mailto:arvi...@exchange.microsoft.com] Sent: Wednesday, November 23, 2016 3:32 PM To: Hertel, Carrie Lynn <carrie.her...@oregonstate.edu>; Josh Spain <jsp...@affinegy.com>; Lioy, Marcello <ml...@qce.qualcomm.com> Cc: allseen-c...@lists.allseenalliance.org Subject: RE: 16.10 is Ready! I too confirm that development is complete and there are no commits in the pipeline. Congratulations everyone who contributed to this release. I think, this release by far is the highest quality release of AllJoyn core! Thanks, Arvind From: Hertel, Carrie Lynn [mailto:carrie.her...@oregonstate.edu] Sent: Wednesday, November 23, 2016 3:08 PM To: Josh Spain <jsp...@affinegy.com>; Marcello Lioy <ml...@qce.qualcomm.com> Cc: allseen-c...@lists.allseenalliance.org; Arvind Padole <arvi...@exchange.microsoft.com> Subject: RE: 16.10 is Ready! QA is complete. ☺ Carrie Hertel, PMP Software Dev Group & Test Lab Director Center for Applied Systems & Software Oregon State University From: Josh Spain [mailto:jsp...@affinegy.com] Sent: Wednesday, November 23, 2016 3:08 PM To: Marcello Lioy <ml...@qce.qualcomm.com<mailto:ml...@qce.qualcomm.com>> Cc: Hertel, Carrie Lynn <carrie.her...@oregonstate.edu<mailto:carrie.her...@oregonstate.edu>>; allseen-c...@lists.allseenalliance.org<mailto:allseen-c...@lists.allseenalliance.org>; Arvind Padole <arvi...@exchange.microsoft.com<mailto:arvi...@exchange.microsoft.com>> Subject: Re: 16.10 is Ready! I see one under review from Paul on the RB16.10 branch, but it is slated for the 16.10a release. Therefore, I confirm the commits are correct and there are no further commits in the pipeline. -Josh On Nov 23, 2016 4:55 PM, "Lioy, Marcello" <ml...@qce.qualcomm.com<mailto:ml...@qce.qualcomm.com>> wrote: Arvind, Josh and Carrie, All of the changes are merged for the 16.10 release, and release candidate builds have been generated. Please confirm: • Everyone: that the v16.10 tag should be placed on the commits identified below • Arvind and Josh: that development is complete and no further commits are in the pipeline. • Carrie: That QA is complete The commit IDs proposed for the v16.10 tag are: alljoyn.git: https://cgit.allseenalliance.org/core/alljoyn.git/commit/?h=RB16.10&id=0cd2ceff303a73f780f14bf012b10ecfe6bc2179 (tagged with : v16.10-rc1<https://cgit.allseenalliance.org/core/alljoyn.git/tag/?h=v16.10-rc1>) ajtcl.git: https://cgit.allseenalliance.org/core/ajtcl.git/commit/?h=RB16.10&id=4ad1cf982012427701991d3e726b4dcc8a852e92 (tagged with: v16.10-rc1<https://cgit.allseenalliance.org/core/ajtcl.git/tag/?h=v16.10-rc1>)
_______________________________________________ Alljoyn-core mailing list Alljoyn-core@lists.alljoyn.org https://lists.alljoyn.org/mailman/listinfo/alljoyn-core