According to this thread[1] the scope for 1.0 was: http://mail-archives.apache.org/mod_mbox/geode-dev/201605.mbox/% 3CCABKA6No4CQmjuzQ4Q0MY5+Nj4=e08jin8losairuoveuf+t...@mail.gmail.com%3E
GEODE-33-2 Create project examples GEODE-1331 gfsh.bat on Windows is incorrect GEODE-1168 geode-dependencies manifest is missing jars that are present in the lib directory GEODE-629 Replace use of org.json with Jackson JSON library GEODE-607 the offheap package needs better unit test coverage GEODE-136 Fix possible NullPointerException in Gfsh's 'list regions' command's GetRegionsFunction. GEODE-1191 HDFS references GEODE-612 Update Jackson version since current version is not on Maven central Rebranding tickets targeted for 1.0 were: GEODE-985 gfsh help text: rebrand for open source 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 >From above, Anthony proposed: GEODE-37 (package renaming) GEODE-1791 (LICENSE update) of these, following issues are still unresolved: GEODE-1168 geode-dependencies manifest is missing jars that are present in the lib directory GEODE-629 Replace use of org.json with Jackson JSON library GEODE-136 Fix possible NullPointerException in Gfsh's 'list regions' command's GetRegionsFunction GEODE-1465 Branding: rename JMX endpoints from 'Gemfire' to 'Geode' GEODE-1466 Branding: rename gemfire.properties file to geode.properties file To me, GEODE-1168 and GEODE-629 do not seem "must have" for 1.0. Also, GEODE-1465 is not immediately user visible, so can be skipped too. However, I think we should target GEODE-17 for 1.0. So, my proposal for issues to be targeted for 1.0 is: GEODE-136 Fix possible NullPointerException in Gfsh's 'list regions' command's GetRegionsFunction GEODE-1466 Branding: rename gemfire.properties file to geode.properties file GEODE-17 Provide Integrated Security GEODE-37 (package renaming) GEODE-1791 (LICENSE update) Thoughts? On Fri, Sep 9, 2016 at 2:56 PM, Dan Smith <dsm...@pivotal.io> wrote: > +1 for getting package renaming in 1.0. > > It would also be nice if we could get some more examples in 1.0! > > -Dan > > On Fri, Sep 9, 2016 at 2:27 PM, Anthony Baker <aba...@pivotal.io> wrote: > > > Thanks for starting this thread. There are a few recent conversations on > > this topic [1][2]. > > > > My thought is that we should bear down and focus on the issues that help > > geode become “graduation-ready”. Here’s a candidate list: > > > > v1.0.0-incubating: > > ----- > > GEODE-37 (package renaming) > > GEODE-1791 (LICENSE update) > > + some bugs fixes as they come in > > > > v1.0.0+ > > ----- > > everything else > > > > > > Looking forward to hearing your thoughts! > > > > Anthony > > > > [1] https://mail-archives.apache.org/mod_mbox/incubator-geode- > > dev/201609.mbox/%3cef2278f9-a216-4f64-8576-c9d091747...@pivotal.io%3e > > [2] http://mail-archives.apache.org/mod_mbox/incubator-geode- > > dev/201609.mbox/%3cCAHEKSULW1J6RWEXqVF_v1Fw9AJimaeXY7gDy5FmjtfkWb2_ > > g...@mail.gmail.com%3e > > > > > On Sep 8, 2016, at 4:24 PM, Swapnil Bawaskar <sbawas...@pivotal.io> > > wrote: > > > > > > I can take on this task for 1.0 > > > > > > On Thu, Sep 8, 2016 at 4:20 PM, William Markito <wmark...@pivotal.io> > > wrote: > > > > > >> With M3 out and all the discussions we're having around what's needed > > for > > >> 1.0, I think we should continue the rotation of release managers and > > get a > > >> new volunteer for 1.0. > > >> > > >> As part of this conversation we should also discuss the scope and > > roadmap > > >> for 1.0 and could use the thread [1] for M3 as a starting point. > > >> > > >> Here is what got discussed: > > >> > > >> ------------- > > >> Guys, restarting this thread to get a discussion going about M3, 1.0.0 > > and > > >> next - As the release manager for M3 here is what I'd like to > propose. > > >> > > >> Any feedback is welcome and let's also reuse this thread to talk a > > little > > >> bit about roadmap as well ? > > >> > > >> # Current M3 Scope (https://cwiki.apache.org/ > > confluence/display/GEODE/1.0. > > >> 0-incubating.M3+Release) > > >> > > >> GEODE-33 > > >> GEODE-823 > > >> GEODE-835 > > >> GEODE-919 > > >> GEODE-1146 > > >> GEODE-1168 > > >> GEODE-1203 > > >> GEODE-1259 > > >> GEODE-1278 > > >> GEODE-1293 > > >> GEODE-1316 > > >> GEODE-1256 > > >> GEODE-1267 > > >> > > >> == Proposed scope & roadmap == > > >> > > >> I'd like to breakdown the release a little bit and already start > > planning > > >> the next releases. > > >> > > >> # Geode 1.0.0-incubating M3 > > >> > > >> GEODE-1316 Update @since tags to include GemFire or Geode in the > version > > >> name > > >> GEODE-1293 Align code and docs for modules > > >> GEODE-1278 AbstractPeerTXRegionStub should throw > > >> TransactionDataNodeHasDeparted when remote cache is closed > > >> GEODE-1267 NOTICE file improvements > > >> GEODE-1256 Geode website - Unapproved licenses > > >> GEODE-1203 gfsh connect --use-http reports a ClassNotFoundException > > >> GEODE-919 GEODE-823 Remove checksums from .asc files (asc.md5, > asc.sha1) > > >> GEODE-835 Replace joptsimple source with a binary dependency > > >> GEODE-823 RC Feedback: Fix build artifacts > > >> GEODE-33-1 Create project examples > > >> > > >> # Geode 1.0.0-incubating > > >> > > >> GEODE-33-2 Create project examples > > >> GEODE-1331 gfsh.bat on Windows is incorrect > > >> GEODE-1168 geode-dependencies manifest is missing jars that are > present > > in > > >> the lib directory > > >> GEODE-629 Replace use of org.json with Jackson JSON library > > >> GEODE-607 the offheap package needs better unit test coverage > > >> GEODE-136 Fix possible NullPointerException in Gfsh's 'list regions' > > >> command's GetRegionsFunction. > > >> > > >> # Geode 1.X.0-incubating > > >> > > >> GEODE-17 Provide Integrated Security > > >> GEODE-11 Lucene Integration > > >> GEODE-33-3 Create project examples > > >> > > >> # Geode 2.0.0-incubating > > >> > > >> GEODE-72 Remove deprecated APIs from Geode > > >> GEODE-37 Package renaming > > >> ------------- > > >> > > >> > > >> [1] http://markmail.org/message/6roww5yc3xhdpdck > > >> -- > > >> ~/William > > >> > > > > >
