I went through and marked ‘Fix Version’ on JIRA’s that were noted in [1]. That’s the last thread I saw discussing release scope.
Apologies if I mis-marked something :-) Anthony [1] http://mail-archives.apache.org/mod_mbox/geode-dev/201602.mbox/%3ccafh+7k1vf2j8fhj98zqewakhfmid+ssdqjmgdqtdowfbhwt...@mail.gmail.com%3E > On Mar 17, 2016, at 3:55 PM, William Markito <[email protected]> wrote: > > Ooops! > > My bad here... I was looking at the link [1] below but that's indeed just > a summary and you're right, it's much more than just those 3, it's actually > 14 according to this query [2] but what's even more funny is that looking > at the Roadmap query by JIRA I have a query [3] showing 10 items (???) > > About 904 looks like Anil assigned to me on 02/Mar/16 23:38 - which is > news, but no problem, let's take a look. > > Also some items there got assigned to M2 by Anthony on 25/Feb/16 which were > not originally part of the initial scope discussed, like GEODE-386... > > From the first Nitin's e-mail, here is what we had: > > 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 > > > > --------------- > > This list definitely wasn't complete by January 29 but then we got another > thread about the scope on March 1st updating and adding more items.... > > [1] > https://issues.apache.org/jira/browse/GEODE/fixforversion/12334709/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel > [2] > https://issues.apache.org/jira/browse/GEODE-27?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.0.0-incubating.M2%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > [3] > https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92&view=planning.nodetail&selectedIssue=GEODE-914 > > > > On Thu, Mar 17, 2016 at 3:20 PM, Dan Smith <[email protected]> wrote: > >> So here's the first thing we need to figure out - what's left to do! >> >> Where did you get those 3 items from William? The M2 wiki page has 17 open >> issues. I think it's displaying the issues marked for the M2 sprint in >> JIRA. Some of those are new subtasks for GEODE-818 I created which maybe >> should be pushed out, but others seem valid. Like GEODE-904, assigned to >> some guy named William :) >> >> >> M2 wiki page: >> >> https://cwiki.apache.org/confluence/display/GEODE/1.0.0-incubating.M2+%28Second%29+Release >> >> Filter for M2 items: >> https://issues.apache.org/jira/issues/?filter=12334915 >> >> On Thu, Mar 17, 2016 at 3:00 PM, William Markito <[email protected]> >> wrote: >> >>> Nice! Thanks Dan & Nitin! >>> >>> Looks like we down to "only" 3 items for M2: >>> >>> [image: Bug] GEODE-27 <https://issues.apache.org/jira/browse/GEODE-27> >>> Apache >>> Geode POM file(s) are incorrect! >>> [image: Bug] GEODE-52 <https://issues.apache.org/jira/browse/GEODE-52> >>> Remove >>> @author tags from Java source >>> [image: Improvement] GEODE-386 >>> <https://issues.apache.org/jira/browse/GEODE-386> Change xsd namespace >> to >>> apache >>> >>> \o/ >>> >>> >>> On Wed, Mar 16, 2016 at 5:51 PM, Nitin Lamba <[email protected]> wrote: >>> >>>> +1 Great idea! >>>> >>>> @Dan, happy to help. I'll update the wiki with some of the e-mails/ >>>> learnings too. >>>> >>>> Nitin >>>> >>>> On Wed, Mar 16, 2016 at 5:29 PM, Dan Smith <[email protected]> wrote: >>>> >>>>> I can give it a shot for M2. I'll have to lean on Nitin and Anthony >> to >>>>> figure out how things worked in the last release, but I think it >> would >>> be >>>>> good to learn. >>>>> >>>>> -Dan >>>>> >>>>> On Wed, Mar 16, 2016 at 4:29 PM, William Markito <[email protected] >>> >>>>> wrote: >>>>> >>>>>> Folks, >>>>>> >>>>>> With the intention of increasing the knowledge about doing a >> release >>>> I'd >>>>>> like to suggest a new release manager (RM) for M2 and then we'd >>> rotate >>>>>> again for M3... >>>>>> >>>>>> The idea here is to get more people to experience the release >> process >>>>> until >>>>>> we have at least 3-5 different committers comfortable with the >>> process, >>>>>> learning and improving it. >>>>>> >>>>>> Any volunteers ? >>>>>> >>>>>> Details about the role: >>>>>> http://www.apache.org/dev/release-publishing.html#release_manager >>>>>> >>>>>> ~/William >>>>>> >>>>> >>>> >>> >>> >>> >>> -- >>> >>> ~/William >>> >> > > > > -- > > ~/William
signature.asc
Description: Message signed with OpenPGP using GPGMail
