geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Huynh <jhu...@pivotal.io>
Subject Re: Last call on 1.2.0 (and fixing test failures)
Date Mon, 15 May 2017 23:09:03 GMT
GEODE-2900 has been checked into develop

On Mon, May 15, 2017 at 3:47 PM Bruce Schuchardt <bschuchardt@pivotal.io>
wrote:

> Yes, GEODE-2915 needs to be fixed for 1.2.0
>
> Le 5/15/2017 à 11:59 AM, Lynn Hughes-Godfrey a écrit :
> > GEODE-2915: Messages rejected due to unknown "vmkind"
> >
> >
> >
> > On Mon, May 15, 2017 at 11:26 AM, Jason Huynh <jhuynh@pivotal.io> wrote:
> >
> >> GEODE-2900 would be nice to get in for Lucene integration.  I hope to
> get
> >> it checked in today
> >>
> >> On Mon, May 15, 2017 at 10:24 AM Swapnil Bawaskar <sbawaskar@pivotal.io
> >
> >> wrote:
> >>
> >>> I think we should also wait for GEODE-2836
> >>>
> >>> On Mon, May 15, 2017 at 8:58 AM Karen Miller <kmiller@pivotal.io>
> wrote:
> >>>
> >>>> Let's finish GEODE-2913, the documentation for improvements made to
> the
> >>>> Lucene integration and include it with the 1.2.0 release!
> >>>>
> >>>>
> >>>> On Sun, May 14, 2017 at 6:47 PM, Anthony Baker <abaker@pivotal.io>
> >>> wrote:
> >>>>> Hi everyone,
> >>>>>
> >>>>> Our last release was v1.1.1 in March.  We have made a lot of great
> >>>>> progress on the develop branch with over 250 issues fixed.  It would
> >> be
> >>>>> great to get those changes into a release.  What’s left before
we are
> >>>> ready
> >>>>> to release 1.2.0?
> >>>>>
> >>>>> Note that we need a clean test run before releasing (except for
> >> “flaky"
> >>>>> tests).  We haven’t had one of those in awhile [1].
> >>>>>
> >>>>> Anthony
> >>>>>
> >>>>> [1] https://builds.apache.org/job/Geode-nightly/
> >>>>> lastCompletedBuild/testReport/
> >>>>>
> >>>>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message