Mailing-List: contact issues-help@mahout.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mahout.apache.org
Date: Wed, 25 Oct 2017 03:31:00 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@mahout.apache.org
Message-ID: <JIRA.13107416.1507255982000.52488.1508902260183@Atlassian.JIRA>
In-Reply-To: <JIRA.13107416.1507255982000@Atlassian.JIRA>
References: <JIRA.13107416.1507255982000@Atlassian.JIRA> <JIRA.13107416.1507255982663@jira-lw-us.apache.org>
Subject: [jira] [Commented] (MAHOUT-2024) Update doap_Mahout.rdf
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 25 Oct 2017 03:31:05 -0000


    [ https://issues.apache.org/jira/browse/MAHOUT-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218049#comment-16218049 ] 

ASF GitHub Bot commented on MAHOUT-2024:
----------------------------------------

GitHub user jackcgai opened a pull request:

    https://github.com/apache/mahout/pull/348

    MAHOUT-2024  Update doap_Mahout.rdf

    ### Purpose of PR:
    Please give a short description of what this PR is for.
    Update the doap_Mahout.rdf file to the current most recent release.
    
    ### Important ToDos
    Please mark each with an "x"
    - [x] A JIRA ticket exists (if not, please create this first)[https://issues.apache.org/jira/browse/ZEPPELIN/]
    - [x] Title of PR is "MAHOUT-XXXX Brief Description of Changes" where XXXX is the JIRA number.
    - [ ] Created unit tests where appropriate
    - [ ] Added licenses correct on newly added files
    - [x ] Assigned JIRA to self
    - [ ] Added documentation in scala docs/java docs, and to website
    - [x] Successfully built and ran all unit tests, verified that all tests pass locally.
    
    If all of these things aren't complete, but you still feel it is
    appropriate to open a PR, please add [WIP] after MAHOUT-XXXX before the
    descriptions- e.g. "MAHOUT-XXXX [WIP] Description of Change"
    
    Does this change break earlier versions?
    no
    Is this the beginning of a larger project for which a feature branch should be made?
    no

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jackcgai/mahout master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/mahout/pull/348.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #348
    
----
commit d0f2e77688f6e92e6661c32e40924477b5abe18b
Author: jackcgai <jackcgai@gmail.com>
Date:   2017-10-23T02:38:07Z

    Add files via upload

commit 5b09db2d8a30e3e49eea3e770fa42ebd824c0962
Author: jackcgai <jackcgai@gmail.com>
Date:   2017-10-23T04:11:34Z

    Merge pull request #1 from jackcgai/jackcgai-patch-2
    
    MAHOUT-2024 Update doap_Mahout.rdf

----


> Update doap_Mahout.rdf
> ----------------------
>
>                 Key: MAHOUT-2024
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-2024
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.13.0
>            Reporter: Andrew Palumbo
>            Assignee: jack ai
>             Fix For: 0.13.1
>
>
> Update the {{doap_Mahout.rdf}} file to the current most recent release.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)