You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by William Markito <wm...@pivotal.io> on 2016/09/08 23:20:32 UTC
M3 is out - New release manager for 1.0 ?
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
Re: M3 is out - New release manager for 1.0 ?
Posted by Swapnil Bawaskar <sb...@pivotal.io>.
For Geode-17:
GEODE-1570 (secure developer REST API) : is in progress, and by the
commits I think its very close to being done.
GEODE-1659 (Prevent misconfiguration of Integrated Security) : has not
been started yet.
everything else has been completed.
So, can we can say GEODE-1570 is targeted for 1.0?
-Swapnil.
On Tue, Sep 20, 2016 at 9:40 AM, Anthony Baker <ab...@pivotal.io> wrote:
> >
> > 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?
> >
>
> I found a few other minor issues that would be good to address in 1.0.0:
>
> GEODE-1513 (duplicate jar files in wars)
> GEODE-1511 (pom dependencies)
>
> I’ve got review requests out for these changes.
>
> Anthony
>
>
Re: M3 is out - New release manager for 1.0 ?
Posted by Anthony Baker <ab...@pivotal.io>.
>
> 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?
>
I found a few other minor issues that would be good to address in 1.0.0:
GEODE-1513 (duplicate jar files in wars)
GEODE-1511 (pom dependencies)
I’ve got review requests out for these changes.
Anthony
Re: M3 is out - New release manager for 1.0 ?
Posted by Michael Stolz <ms...@pivotal.io>.
I think we should do these security features incrementally after 1.0.0.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Mon, Sep 19, 2016 at 6:16 PM, Anthony Baker <ab...@pivotal.io> wrote:
>
> > On Sep 17, 2016, at 5:29 PM, Swapnil Bawaskar <sb...@pivotal.io>
> wrote:
> >
> > 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)
>
> GEODE-17 implies:
> GEODE-1569 (add post authorization processing in JMX and CLI
> commands)
> GEODE-1570 (secure developer REST API)
> GEODE-1571 (Client security should be able to use
> Resource:Operation permissions)
> GEODE-1648 (Provide ability to disable security for some
> components) **
> GEODE-1643 (The new SecurityManager need to authenticate the
> gateway sender/receiver as well)
> GEODE-1659 (Prevent misconfiguration of Integrated Security)
>
> Were you thinking all these security enhancements should be included in
> 1.0.0? Seems like that could potentially be a lengthy process. Does it
> make sense to release at these changes incrementally?
>
> The other items in scope for 1.0.0 look good to me.
>
> Anthony
>
>
> ** there was a recent discussion on this topic where the suggestion was to
> not allow per-component RBAC configuration: https://mail-archives.apache.
> org/mod_mbox/incubator-geode-dev/201609.mbox/%
> 3cCANgOuWsSFmSZBmLV9eq2KaVgjtJ_T2f1AD-QrA8gZQMEq4tvTw@mail.gmail.com%3e
>
>
>
Re: M3 is out - New release manager for 1.0 ?
Posted by Anthony Baker <ab...@pivotal.io>.
> On Sep 17, 2016, at 5:29 PM, Swapnil Bawaskar <sb...@pivotal.io> wrote:
>
> 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)
GEODE-17 implies:
GEODE-1569 (add post authorization processing in JMX and CLI commands)
GEODE-1570 (secure developer REST API)
GEODE-1571 (Client security should be able to use Resource:Operation permissions)
GEODE-1648 (Provide ability to disable security for some components) **
GEODE-1643 (The new SecurityManager need to authenticate the gateway sender/receiver as well)
GEODE-1659 (Prevent misconfiguration of Integrated Security)
Were you thinking all these security enhancements should be included in 1.0.0? Seems like that could potentially be a lengthy process. Does it make sense to release at these changes incrementally?
The other items in scope for 1.0.0 look good to me.
Anthony
** there was a recent discussion on this topic where the suggestion was to not allow per-component RBAC configuration: https://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201609.mbox/%3cCANgOuWsSFmSZBmLV9eq2KaVgjtJ_T2f1AD-QrA8gZQMEq4tvTw@mail.gmail.com%3e
Re: M3 is out - New release manager for 1.0 ?
Posted by Swapnil Bawaskar <sb...@pivotal.io>.
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+Txaw@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 <ds...@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 <ab...@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-C9D091747450@pivotal.io%3e
> > [2] http://mail-archives.apache.org/mod_mbox/incubator-geode-
> > dev/201609.mbox/%3cCAHEKSULW1J6RWEXqVF_v1Fw9AJimaeXY7gDy5FmjtfkWb2_
> > gMw@mail.gmail.com%3e
> >
> > > On Sep 8, 2016, at 4:24 PM, Swapnil Bawaskar <sb...@pivotal.io>
> > wrote:
> > >
> > > I can take on this task for 1.0
> > >
> > > On Thu, Sep 8, 2016 at 4:20 PM, William Markito <wm...@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
> > >>
> >
> >
>
Re: M3 is out - New release manager for 1.0 ?
Posted by Dan Smith <ds...@pivotal.io>.
+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 <ab...@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-C9D091747450@pivotal.io%3e
> [2] http://mail-archives.apache.org/mod_mbox/incubator-geode-
> dev/201609.mbox/%3cCAHEKSULW1J6RWEXqVF_v1Fw9AJimaeXY7gDy5FmjtfkWb2_
> gMw@mail.gmail.com%3e
>
> > On Sep 8, 2016, at 4:24 PM, Swapnil Bawaskar <sb...@pivotal.io>
> wrote:
> >
> > I can take on this task for 1.0
> >
> > On Thu, Sep 8, 2016 at 4:20 PM, William Markito <wm...@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
> >>
>
>
Re: M3 is out - New release manager for 1.0 ?
Posted by Anthony Baker <ab...@pivotal.io>.
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-C9D091747450@pivotal.io%3e
[2] http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201609.mbox/%3cCAHEKSULW1J6RWEXqVF_v1Fw9AJimaeXY7gDy5FmjtfkWb2_gMw@mail.gmail.com%3e
> On Sep 8, 2016, at 4:24 PM, Swapnil Bawaskar <sb...@pivotal.io> wrote:
>
> I can take on this task for 1.0
>
> On Thu, Sep 8, 2016 at 4:20 PM, William Markito <wm...@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
>>
Re: M3 is out - New release manager for 1.0 ?
Posted by Swapnil Bawaskar <sb...@pivotal.io>.
I can take on this task for 1.0
On Thu, Sep 8, 2016 at 4:20 PM, William Markito <wm...@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
>