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 <[email protected]> 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 <[email protected]> > 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 <[email protected]> > 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 <[email protected]> > > 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/ > > > > > >
