I walked through JIRA this morning.  There’s a lot of really interesting stuff 
we should consider for M2.  However, I think we should err on the conservative 
side given that we already have a lot of work in flight (e.g. Pulse, Modules, 
WAN, CQ, etc) and we don’t want to run too long before our next release.  Given 
the new code additions, I would expect 2-3 RC’s will be needed.

I’ve grouped and stack ranked the tickets that seem relevant to M2 below.  This 
is just IMO and I would appreciate community input on this.

Tests:
GEODE-944 (Test failure when ISP intercepts DNS failure)
RC2 test failures from Brian Dunlap [1]
----- ^ M2 ^ -----

Security:
GEODE-562 (Remove or upgrade commons-collections)
----- ^ M2 ^ -----

IP:
GEODE-906 (Cleanup source headers)
GEODE-905 (Source headers)
GEODE-901 (Source headers)
GEODE-907 (Remove JSON code from pulse)
GEODE-903 (Copyright date on footer)
GEODE-914 (NOTICE)
GEODE-904 (LICENSE)
GEODE-918 (Add license header to generated pom)
----- ^ M2 ^ ----- v M3 v -----
GEODE-835 (remove gemfire-joptsimple)
GEODE-629 (JSON parser)
GEODE-868 (Autogenerate NOTICE)

Maven:
GEODE-26 (remove mavenLocal)
GEODE-917 (rename artifacts to geode)
GEODE-27 (Maven POM)
GEODE-946 (maven artifacts)
----- ^ M2 ^ ----- v M3 v -----
GEODE-919 (Don’t checksum signature files)

Docs:
GEODE-945 (Javadoc warning)
GEODE-54 (javadocs)
GEODE-887 (README)
GEODE-884 (README)
GEODE-876 (Add README to binary distro)
GEODE-874 (COMPILING / RUNNING)
----- ^ M2 ^ ----- v M3 v -----
GEODE-33 (example code)

Other:
GEODE-12 (Pulse)
----- ^ M2 ^ ----- v M3 v -----
GEODE-25 (crypto audit)
GEODE-786 (Update SDG to 1.7.2)
GEODE-543 (Upgrade jline and spring shell)
GEODE-57 (Update library versions)
GEODE-52 (@author)
GEODE-37 (package renaming)
GEODE-36 (Rename gfsh)


Anthony

[1] 
http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201601.mbox/%3ccafdh8_1cuvs36a7yppjod9b4k1cip_p8kepkxn+wbxe4kzq...@mail.gmail.com%3e


> On Feb 5, 2016, at 3:39 PM, Nitin Lamba <[email protected]> wrote:
> 
> Thanks Dan!
> We should perhaps discuss this topic in detail during our next Geode 
> Clubhouse.
> 
> @Mike, agree 100% with your prioritization though WAN and CQ have already 
> been merged with develop. So unless any testing/ performance issues pop-up, 
> we'll get those included as part of the next milestone release automatically.
> 
> - Nitin
> 
> ________________________________________
> From: Dan Smith <[email protected]>
> Sent: Thursday, February 4, 2016 1:46 PM
> To: geode
> Subject: Re: [DISCUSS] Next Release Scope - version 1.0.0-incubating.M2
> 
> I added the bugs listed above, and a some others, to the M2 wiki page so we
> don't lose track of them. We can discuss if some of these need to get
> pushed out of M2.
> 
> I also created some subtasks for GEODE-823.
> 
> On Mon, Feb 1, 2016 at 7:09 AM, Michael Stolz <[email protected]> wrote:
> 
>> I'd like to see the focus on docs and dependencies first.
>> Then incorporation of WAN and CQ features.
>> 
>> --
>> Mike Stolz
>> Principal Engineer, GemFire Product Manager
>> Mobile: 631-835-4771
>> 
>> On Fri, Jan 29, 2016 at 12:26 PM, Nitin Lamba <[email protected]> wrote:
>> 
>>> Thought of starting a separate thread to discuss next release scope. So
>>> far we have the following suggestions:
>>> 
>>> Dan:
>>> - GEODE-823 - remove gemfire-joptsimple, gemfire-json, rename to geode-,
>>> other misc issues
>>> - GEODE-818 - clean up dependencies
>>> - GEODE-572 - generate public javadocs (part of GEODE-54)
>>> - GEODE-33 - create project examples
>>> 
>>> John:
>>> - GEODE-27 - fix POM dependencies - related to RC feedback above
>>> (GEODE-818)
>>> 
>>> Few left-over from prior discussions:
>>> 
>>> - GEODE-386 - fixing xsd namespace to Apache
>>> - GEODE-36 - fixing gfsh cli (Removing GemFire references)
>>> - GEODE-37 - package re-naming
>>> 
>>> Some of these are big ticket items so we may have to space these out
>>> across Milestones.
>>> 
>>> ACTION: Please suggest on this thread OR edit the wiki page[1] so that
>>> JIRA [2] can be prioritized accordingly.
>>> 
>>> Thanks,
>>> Nitin
>>> 
>>> [1]
>>> 
>> https://cwiki.apache.org/confluence/display/GEODE/1.0.0-incubating.M2+%28Second%29+Release
>>> [2]
>>> 
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92&view=planning
>>> 
>>> 
>> 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to