[jira] [Work logged] (MAHOUT-2076) add a /release directory with a skeleton settings.xml for releases

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAHOUT-2076?focusedWorklogId=348011&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-348011 ]

ASF GitHub Bot logged work on MAHOUT-2076:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Nov/19 08:55
            Start Date: 22/Nov/19 08:55
    Worklog Time Spent: 10m 
      Work Description: andrewpalumbo commented on pull request #384: [MAHOUT-2076]: add a /release directory with a skeleton settings.xml …
URL: https://github.com/apache/mahout/pull/384
 
 
   …for releases
   
   ### Purpose of PR:
   Please give a short description of what this PR is for.
   
   
   ### 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/mahout/]
   - [X ] Title of PR is "MAHOUT-XXXX Brief Description of Changes" where XXXX is the JIRA number.
   - [X ] Created unit tests where appropriate
   - [X] Added licenses correct on newly added files
   - [ X] Assigned JIRA to self
   - [  ] Added documentation in scala docs/java docs, and to website
   - [ N/A ] 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?
   
   Yes, but no feature branch,
   
   I'd like to start an effort to "Scale Down" some mahout data-structures so that they can be concatanated into DRMs, Still, but optimized for specific devices, possibly nativly.  This also could be a sub-project It is something that I may have use for, and hopefully can build in down the line. I bring this up hwen i get a chance on  dev@.  
   
   This itself necessary for anybody who wants to do an apace release.  It is also nice for a developer who clones the branch at the office, to be able to deploy to a local repository. an needs a `README.md`
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 348011)
    Remaining Estimate: 0h
            Time Spent: 10m

> add a /release directory with a skeleton settings.xml for releases
> ------------------------------------------------------------------
>
>                 Key: MAHOUT-2076
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-2076
>             Project: Mahout
>          Issue Type: New Feature
>          Components: release
>    Affects Versions: 0.14.0
>            Reporter: Andrew Palumbo
>            Assignee: Andrew Palumbo
>            Priority: Minor
>             Fix For: 14.1
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> add a  {{/release}} diectory with {{settins.xm}}l and all necessary variable changes to make a release with {{mvn release:prepare -Papache-release}} and



--
This message was sent by Atlassian Jira
(v8.3.4#803005)