OK, I've added a couple of JIRA filters to extract all issues loaded in our M2 sprint. This helps create a data-driven table of issues on the wiki page [1] instead of manually sync-ing it. Ideally, we should start this (scope-defined) sprint and close it when M2 is released. Thoughts?
Please check it out and suggest if any specific attributes should be displayed or if the inclusion/ exclusion criteria should be changed. Nitin [1] https://cwiki.apache.org/confluence/display/GEODE/1.0.0-incubating.M2+%28Second%29+Release ________________________________________ From: Nitin Lamba <[email protected]> Sent: Tuesday, March 1, 2016 1:17 PM To: [email protected] Subject: Re: Scope for M2 release +1 I had recently updated the wiki page for completed JIRAs. Ideally, we should just have one place to update. Let me quickly research if there's a way to integrate the lists. Nitin ________________________________________ From: Kirk Lund <[email protected]> Sent: Tuesday, March 1, 2016 11:33 AM To: [email protected] Subject: Re: Scope for M2 release +1 On Tuesday, March 1, 2016, Anthony Baker <[email protected]> wrote: > I was discussing the M2 release scope and noticed that the wiki page [1] > differs slightly from the JIRA Geode-Release filter [2] and roadmap [3], > > Should we update the wiki page to match JIRA based on the prior email > thread [4]? > > Anthony > > [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.nodetail&selectedIssue=GEODE-914 > [3] > https://cwiki.apache.org/confluence/display/GEODE/1.0.0-incubating.M2+%28Second%29+Release > [4] > http://mail-archives.apache.org/mod_mbox/geode-dev/201602.mbox/%3ccafh+7k1vf2j8fhj98zqewakhfmid+ssdqjmgdqtdowfbhwt...@mail.gmail.com%3E >
