I have filed https://issues.apache.org/jira/browse/GEODE-1598 which may have been caused by fixing GEODE-835.
In my opinion GEODE-1598 should be fixed before we release M3. On Tue, Jun 21, 2016 at 12:04 AM, William Markito <wmark...@pivotal.io> wrote: > Just pushed GEODE-33 [1] for review. > > [1] https://github.com/apache/incubator-geode/tree/feature/GEODE-33 > > On Fri, Jun 17, 2016 at 6:05 PM, Kirk Lund <kl...@pivotal.io> wrote: > > > Yep, huge thanks to Grace Meilen for finishing up GEODE-835! > > > > -Kirk > > > > On Friday, June 17, 2016, Swapnil Bawaskar <sbawas...@pivotal.io> wrote: > > > > > GEODE-835 has been fixed. Do we have any progress on GEODE-1493? > > > > > > On Wed, Jun 15, 2016 at 10:20 AM, Sai Boorlagadda < > > > sai.boorlaga...@gmail.com <javascript:;> > > > > wrote: > > > > > > > i will give a try fixing GEODE-1493. > > > > > > > > Sai > > > > > > > > On Wed, Jun 15, 2016 at 10:17 AM, Dan Smith <dsm...@pivotal.io > > > <javascript:;>> wrote: > > > > > > > > > I think we should fix GEODE-1493 for M3 - we shouldn't be shipping > > > > > foldernames from the release manager's filesystem in the binary > > > release. > > > > I > > > > > can look into it if no one else is interested. > > > > > > > > > > -Dan > > > > > > > > > > On Wed, Jun 15, 2016 at 10:04 AM, Darrel Schneider < > > > > dschnei...@pivotal.io <javascript:;>> > > > > > wrote: > > > > > > > > > > > The test failing in GEODE-840 I think is going to be classified > as > > > > > "flaky". > > > > > > It should not hold up the m3 release. > > > > > > > > > > > > > > > > > > On Wed, Jun 15, 2016 at 10:02 AM, Anilkumar Gingade < > > > > aging...@pivotal.io <javascript:;> > > > > > > > > > > > > wrote: > > > > > > > > > > > > > GEODE-1493 > > > > > > > Its not assigned to anyone...Someone with gradle/build > experience > > > can > > > > > > pick > > > > > > > this up....Doesn't seems to be a stopper for M3. > > > > > > > > > > > > > > GEODE-835 > > > > > > > In progress, kirk can comment on this. > > > > > > > > > > > > > > -Anil. > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Jun 15, 2016 at 9:48 AM, Gregory Chase < > > gch...@pivotal.io > > > <javascript:;>> > > > > > > wrote: > > > > > > > > > > > > > > > Should GEODE-33 be broken up into specific tickets? > > > > > > > > > > > > > > > > What do we want examples for? > > > > > > > > > > > > > > > > This might be easier for many of the expert users to actually > > > make > > > > > > > > contributions. > > > > > > > > > > > > > > > > -Greg > > > > > > > > > > > > > > > > On Wed, Jun 15, 2016 at 9:40 AM, Anthony Baker < > > > aba...@pivotal.io <javascript:;>> > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi I reviewed the JIRA’s tagged for the M3 release. The > good > > > > news > > > > > is > > > > > > > > that > > > > > > > > > we’ve fixed 180 issues! Here are the remaining open > issues: > > > > > > > > > > > > > > > > > > GEODE-33: Project examples > > > > > > > > > GEODE-835: joptsimple replacement > > > > > > > > > GEODE-840: CI failure in > > > > > > > > > > > > DistributedAckPersistentRegionCCEOffHeapDUnitTest.testTombstones > > > > > > > > > GEODE-1493: gemfire.properties default value for config dir > > > > > > > > > > > > > > > > > > Any sense for when these issues will be resolved? Which > ones > > > are > > > > > > > > required > > > > > > > > > for M3? > > > > > > > > > > > > > > > > > > Anthony > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Greg Chase > > > > > > > > > > > > > > > > Global Head, Big Data Communities > > > > > > > > http://www.pivotal.io/big-data > > > > > > > > > > > > > > > > Pivotal Software > > > > > > > > http://www.pivotal.io/ > > > > > > > > > > > > > > > > 650-215-0477 > > > > > > > > @GregChase > > > > > > > > Blog: http://geekmarketing.biz/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > ~/William >
