Re: M3 status?

2016-07-07 Thread Kirk Lund
Here are the open branding tickets I'm aware of: GEODE-1465: Branding: rename JMX endpoints from 'Gemfire' to 'Geode' GEODE-1466: Branding: rename gemfire.properties file to geode.properties file GEODE-1467: Branding: Rename servlet URLs from gemfire to geode GEODE-1566: Branding: GemFireRedisServ

Re: M3 status?

2016-07-07 Thread Nitin Lamba
Are the remaining branding JIRAs planned in M3? I saw gfsh help fixed [1] but others (JMX, REST end-points) are still open. Thanks, Nitin [1] http://issues.apache.org/jira/browse/GEODE-985 On Thu, Jul 7, 2016 at 1:38 PM, William Markito wrote: > Thanks for the update Jinmei! Will hold until to

Re: M3 status?

2016-07-07 Thread William Markito
Thanks for the update Jinmei! Will hold until tomorrow for cutting the branch. Thanks! On Thu, Jul 7, 2016 at 11:21 AM, Jinmei Liao wrote: > Hey, Kirk, Grade, Kevin and I are working on this new security feature > that's almost complete which would be nice to be included in M3. Could you > plea

Re: M3 status?

2016-07-07 Thread Jinmei Liao
Hey, Kirk, Grade, Kevin and I are working on this new security feature that's almost complete which would be nice to be included in M3. Could you please wait till tomorrow to cut the branch? Thanks! On Fri, Jul 1, 2016 at 6:18 PM, William Markito wrote: > Given the recent changes on develop (*jo

Re: M3 status?

2016-07-01 Thread William Markito
Given the recent changes on develop (*jopt-simple*) I'm planning to cut the M3 release branch late next week (Wednesday/Thursday) - So please speak up if you think otherwise... ;) Thanks! On Mon, Jun 27, 2016 at 5:50 PM, Kirk Lund wrote: > Grace and I started looking into this today. The forke

Re: M3 status?

2016-06-27 Thread Kirk Lund
Grace and I started looking into this today. The forked version of jopt-simple was returning a list of detected options that was being used during auto-complete. She came up with what looks like a good work-around in GFSH code that should be completed and merged to develop this week. -Kirk On Mon

Re: M3 status?

2016-06-27 Thread Swapnil Bawaskar
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 wrote: > Just pushed GEODE-33 [1] for review. > > [1] https://github.com

Re: M3 status?

2016-06-21 Thread William Markito
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 wrote: > Yep, huge thanks to Grace Meilen for finishing up GEODE-835! > > -Kirk > > On Friday, June 17, 2016, Swapnil Bawaskar wrote: > > > GEODE-

Re: M3 status?

2016-06-17 Thread Kirk Lund
Yep, huge thanks to Grace Meilen for finishing up GEODE-835! -Kirk On Friday, June 17, 2016, Swapnil Bawaskar 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 > > wrote: > > > i will gi

Re: M3 status?

2016-06-17 Thread Sai Boorlagadda
GEODE-1493 is resolved. On Fri, Jun 17, 2016 at 11:48 AM, Swapnil Bawaskar 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 > > wrote: > > > i will give a try fixing GEODE-1493. > > > > S

Re: M3 status?

2016-06-17 Thread Swapnil Bawaskar
GEODE-835 has been fixed. Do we have any progress on GEODE-1493? On Wed, Jun 15, 2016 at 10:20 AM, Sai Boorlagadda wrote: > i will give a try fixing GEODE-1493. > > Sai > > On Wed, Jun 15, 2016 at 10:17 AM, Dan Smith wrote: > > > I think we should fix GEODE-1493 for M3 - we shouldn't be shippin

Re: M3 status?

2016-06-15 Thread Sai Boorlagadda
i will give a try fixing GEODE-1493. Sai On Wed, Jun 15, 2016 at 10:17 AM, Dan Smith 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

Re: M3 status?

2016-06-15 Thread Dan Smith
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 wrote: > The test failing in GEODE-840 I think is

Re: M3 status?

2016-06-15 Thread Darrel Schneider
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 wrote: > GEODE-1493 > Its not assigned to anyone...Someone with gradle/build experience can pick > this upDoesn't seems to be

Re: M3 status?

2016-06-15 Thread Anilkumar Gingade
GEODE-1493 Its not assigned to anyone...Someone with gradle/build experience can pick this upDoesn'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 wrote: > Should GEODE-33 be broken up into specific ti

Re: M3 status?

2016-06-15 Thread Gregory Chase
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 wrote: > Hi I reviewed the JIRA’s tagged for the M3 release. The good news

M3 status?

2016-06-15 Thread Anthony Baker
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-149