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: GemFireRedisServer should be renamed as GeodeRedisServer
No one has taken on 1465/1466/1467 or submitted a PR for any of them so I believe they will not be in M3. Grace Meilen submitted a PR fixing GEODE-1566, so we can probably commit that one tomorrow to be included in M3 after reviewing the test results. Cheers, Kirk On Thu, Jul 7, 2016 at 4:29 PM, Nitin Lamba <nitin.la...@gmail.com> wrote: > 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 <wmark...@pivotal.io> > wrote: > > > 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 <jil...@pivotal.io> 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 > > > please wait till tomorrow to cut the branch? Thanks! > > > > > > On Fri, Jul 1, 2016 at 6:18 PM, William Markito <wmark...@pivotal.io> > > > wrote: > > > > > > > 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 <kl...@apache.org> wrote: > > > > > > > > > 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, Jun 27, 2016 at 11:14 AM, Swapnil Bawaskar < > > > sbawas...@pivotal.io > > > > > > > > > > wrote: > > > > > > 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 > > > > > >> > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > ~/William > > > > > > > > > > > > > > > > -- > > > Cheers > > > > > > Jinmei > > > > > > > > > > > -- > > > > ~/William > > >
