I confirm that the v16.10.02 tag should be placed on the commits identified in the email from Josh.
On Aug 2, 2017, at 9:57 AM, Krystian Zlomek <kzlo...@affinegy.com> wrote: > I also confirm that both commits are correct for v16.10.02 tag. > > Regards, > Krystian > > On Wed, Aug 2, 2017 at 4:48 PM, Karol Matuszkiewicz > <kmatuszkiew...@affinegy.com> wrote: > I confirm that the v16.10.02 tag should be placed on the commits identified > in the email from Josh. > > Regards, > Karol > > On Tue, Aug 1, 2017 at 9:00 PM, Josh Spain <jsp...@affinegy.com> wrote: > AllJoyn Core 16.10.02 Team: > > All of the changes are merged for the 16.10.02 release, and release candidate > builds have been generated. I confirm that development is complete and no > further commits are in the pipeline. > > Team, please confirm the following by replying to all: > Committers: that the v16.10.02 tag should be placed on the commits identified > below > Carrie: that QA is complete > The commit IDs proposed for the v16.10.02 tag are: > > alljoyn.git: > https://cgit.allseenalliance.org/core/alljoyn.git/commit/?id=43cce3fbb24b5cacc54d4cb2b823cab1c7bb41df > (tagged with: v16.10.02-rc1) > > ajtcl.git: > https://cgit.allseenalliance.org/core/ajtcl.git/commit/?h=refs/heads/RB16.10&id=579f77a0518a1bb3c6461f367de7a9b24c882f14 > (tagged with: v16.10.02-rc1) > > -Josh > > >
_______________________________________________ Alljoyn-core mailing list Alljoyn-core@lists.alljoyn.org https://lists.alljoyn.org/mailman/listinfo/alljoyn-core
