+1

* verified commit hash
* checked concourse pipeline is green
* ran examples with RC1
* built from source

Sai

On Wed, Sep 19, 2018 at 8:46 AM Nabarun Nag <n...@pivotal.io> wrote:

> REMINDER: VOTE deadline is today (EOD 19th September 2018 PDT)
>
> Regards
> Nabarun Nag
>
> On Wed, Sep 19, 2018 at 7:13 AM Anthony Baker <aba...@pivotal.io> wrote:
>
> > I think we can get rid of the **/out/** exclusion in the build script,
> > let’s do that for the next release.
> >
> > Anthony
> >
> >
> > > On Sep 18, 2018, at 3:52 PM, Dan Smith <dsm...@pivotal.io> wrote:
> > >
> > > +0
> > >
> > > I noticed that someone added some files called "out" to the repo that
> > > aren't included in the source distribution:
> > >
> > > ./ci/resource-types/gce-instances-resource/out
> > > ./ci/resource-types/concourse-metadata-resource/files/out
> > >
> > > These aren't included in the source distribution because we are
> > explicitly
> > > excluding anything called "out." Presumably we thought anything called
> > out
> > > is an output directory ("out" is also in .gitignore). So the ci
> directory
> > > in the source distribution is incomplete. But maybe that doesn't matter
> > > because it is just CI configuration?
> > >
> > > Everything else looks good.
> > >
> > > -Dan
> > >
> > > On Mon, Sep 17, 2018 at 5:06 PM, Nabarun Nag <n...@apache.org> wrote:
> > >
> > >> *DEADLINE :* Kindly complete your vote by Wednesday, 19th September
> > 2018.
> > >> End of day PDT.
> > >>
> > >> Following checks completed:
> > >>
> > >> - checked signatures
> > >> - checked sha’s
> > >> - builds from source
> > >> - run gfsh - start locator, server - create region - do put and get -
> > >> execute OQL query
> > >> - examples run cleanly
> > >>
> > >> @John Blum <jb...@pivotal.io> , I was looking into the mail chain for
> > >> Apache Geode 1.5.0 RC and I saw that you had some concerns regarding
> SD
> > >> Geode's behavior with the changes made to Log4j in Apache Geode. In
> this
> > >> release, too we have made some upgrades to log4j and we would to hear
> > your
> > >> feedback / get a green light on these changes.
> > >>
> > >> Regards
> > >> Nabarun Nag
> > >>
> > >>
> > >>
> > >> On Fri, Sep 14, 2018 at 2:50 PM Nabarun Nag <n...@apache.org> wrote:
> > >>
> > >>> Correction :
> > >>> Please note that we are voting upon the source tags: rel/v1.7.0.RC1
> > >>>
> > >>> On Fri, Sep 14, 2018 at 2:49 PM Nabarun Nag <n...@apache.org> wrote:
> > >>>
> > >>>> This is the first release candidate for Apache Geode, version 1.7.0.
> > >>>> Thanks to all the community members for their contributions to this
> > >>>> release!
> > >>>>
> > >>>> Please do review and give your feedback.
> > >>>>
> > >>>> 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.6.0.RC1
> > >>>> Apache Geode:
> > >>>> https://github.com/apache/geode/tree/rel/v1.7.0.RC1
> > >>>> Apache Geode examples:
> > >>>> https://github.com/apache/geode-examples/tree/rel/v1.7.0.RC1
> > >>>>
> > >>>> Commit ID:
> > >>>> Apache Geode:
> > >>>> f9abdeb489c9278f96afd37f72a7a9d14cb0f154
> > >>>> Apache Geode Examples:
> > >>>> 9dca29c7c10fa8d44abc893271420476cfc0808f
> > >>>>
> > >>>>
> > >>>> Source and binary files:
> > >>>> https://dist.apache.org/repos/dist/dev/geode/1.7.0.RC1/
> > >>>>
> > >>>> Maven staging repo:
> > >>>>
> > https://repository.apache.org/content/repositories/orgapachegeode-1042
> > >>>>
> > >>>> 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.
> > >>>>
> > >>>> Regards
> > >>>> Nabarun Nag
> > >>>>
> > >>>
> > >>
> >
> >
>

Reply via email to