I will be checking in rolling-upgrade testing against 1.1.1 with my fix
for GEODE-2915
Le 5/15/2017 à 5:07 PM, Lynn Hughes-Godfrey a écrit :
We need to ensure we have backward compatibility and rolling upgrade
capability/testing with geode 1.1.
-l-
On Mon, May 15, 2017 at 4:09 PM, Jason Huynh <jhu...@pivotal.io> wrote:
GEODE-2900 has been checked into develop
On Mon, May 15, 2017 at 3:47 PM Bruce Schuchardt <bschucha...@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 <jhu...@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 <
sbawas...@pivotal.io
wrote:
I think we should also wait for GEODE-2836
On Mon, May 15, 2017 at 8:58 AM Karen Miller <kmil...@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 <aba...@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/
