+1

Ran geode-release-check. Verified pipeline is green. Looks good!

-Dan

On Tue, Oct 2, 2018 at 11:50 AM Anthony Baker <aba...@pivotal.io> wrote:

> +1
>
> - verified sha’s and signatures
> - checked source release for binaries
> - verified geode source build
> - verified geode binary distribution
> - verified geode-examples source build
> - verified git tag
>
> Anthony
>
>
> > On Oct 1, 2018, at 10:01 AM, Ryan McMahon <mcmellaw...@apache.org>
> wrote:
> >
> > +1
> >
> > - Verified clean build from source
> > - Built and ran all geode-examples
> >
> > On Fri, Sep 28, 2018 at 8:52 PM Sai Boorlagadda <
> sai.boorlaga...@gmail.com>
> > wrote:
> >
> >> +1
> >>
> >> * verified signatures
> >>
> >> * verified source distribution builds
> >>
> >> * ran basic gfsh commands
> >>
> >> * started pulse
> >>
> >> * verified examples work with rc2
> >>
> >>
> >> Sai
> >>
> >> On Fri, Sep 28, 2018 at 8:57 AM Dave Barnes <dbar...@pivotal.io> wrote:
> >>
> >>> +1
> >>> Downloaded the release & successfully ran some representative gfsh
> >>> commands.
> >>> There is still a problem that I noted in my RC1 review: the user guide
> >>> config files incorrectly specify v1.8.
> >>> This is not a showstopper, but this time I have created a JIRA ticket
> >>> (GEODE-5795) so if (heaven forfend) we roll an RC3, the correction will
> >> be
> >>> included.
> >>>
> >>> On Thu, Sep 27, 2018 at 7:13 PM, Nabarun Nag <n...@apache.org> wrote:
> >>>
> >>>> Following checks completed:
> >>>> - checked signatures -src.tgz -examples.tgz -.tgz
> >>>> - checked SHA's -src.tgz -examples.tgz -.tgz
> >>>> - builds from source
> >>>> - run gfsh - start locator, server - create region - do put and get -
> >>>> execute OQL query
> >>>> - examples run cleanly
> >>>> - the correct version in gfsh command version
> >>>> - out scripts are now present in the source distribution
> >>>>    -> ./ci/resource-types/gce-instances-resource/out
> >>>>    -> ./ci/resource-types/concourse-metadata-resource/files/out
> >>>>
> >>>> Regrads
> >>>> Nabarun Nag
> >>>>
> >>>>
> >>>> On Thu, Sep 27, 2018 at 6:54 PM Nabarun Nag <n...@apache.org> wrote:
> >>>>
> >>>>> This is the second release candidate for Apache Geode, version 1.7.0.
> >>>>> Thanks to all the community members for their contributions to this
> >>>>> release!
> >>>>>
> >>>>> Please do a review and give your feedback. The deadline is the end of
> >>> day
> >>>>> 2nd October 2018.
> >>>>>
> >>>>> It resolves 351 issues on Apache Geode JIRA system. Release notes can
> >>> be
> >>>>> found at:
> >>>>> https://cwiki.apache.org/confluence/display/GEODE/
> >>>>> Release+Notes#ReleaseNotes-1.7.0
> >>>>>
> >>>>>
> >>>>> Please note that we are voting upon the source tags: rel/v1.7.0.RC2
> >>>>> Apache Geode:
> >>>>> https://github.com/apache/geode/tree/rel/v1.7.0.RC2
> >>>>> Apache Geode examples:
> >>>>> https://github.com/apache/geode-examples/tree/rel/v1.7.0.RC2
> >>>>>
> >>>>> Commit ID:
> >>>>> Apache Geode:
> >>>>> 48061cdcc293d42020b8695a5a23c4dd360550ff
> >>>>> Apache Geode Examples:
> >>>>> 9dca29c7c10fa8d44abc893271420476cfc0808f
> >>>>>
> >>>>>
> >>>>> Source and binary files:
> >>>>> https://dist.apache.org/repos/dist/dev/geode/1.7.0.RC2/
> >>>>>
> >>>>> Maven staging repo:
> >>>>>
> >> https://repository.apache.org/content/repositories/orgapachegeode-1046
> >>>>>
> >>>>> Geode's KEYS file containing PGP keys we use to sign the release:
> >>>>> https://github.com/apache/geode/blob/develop/KEYS
> >>>>>
> >>>>> Signed the release with fingerprint:
> >>>>> rsa4096 2018-01-04 [SC] [expires: 2022-01-04]
> >>>>> CE6CD0A89480B1B9FCB98699274C66710770C135
> >>>>>
> >>>>> rsa4096 2018-01-04 [SC] [expires: 2022-01-04]
> >>>>>
> >>>>> I do apologize if there was an oversight.
> >>>>>
> >>>>> PS: Command to run geode-examples: ./gradlew -PgeodeReleaseUrl=
> >>>>> https://dist.apache.org/repos/dist/dev/geode/1.7.0.RC2
> >>>>> -PgeodeRepositoryUrl=
> >>>>>
> >> https://repository.apache.org/content/repositories/orgapachegeode-1046
> >>>>> build runAll
> >>>>>
> >>>>> Regards
> >>>>> Nabarun Nag
> >>>>>
> >>>>
> >>>
> >>
>
>

Reply via email to