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

ASF GitHub Bot commented on USERGRID-758:
-----------------------------------------

GitHub user snoopdave opened a pull request:

    https://github.com/apache/incubator-usergrid/pull/293

    Introduce a version number in the WAR file name for USERGRID-758

    subject says it all

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

    $ git pull https://github.com/apache/incubator-usergrid USERGRID-758

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

    https://github.com/apache/incubator-usergrid/pull/293.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 #293
    
----
commit 77925e76bc38ba42aff786d55575fccad3526160
Author: Dave Johnson <snoopd...@gmail.com>
Date:   2015-06-29T13:54:52Z

    Introduce a version number in the WAR file name for USERGRID-758

----


> Introduce Semantic Versioning in Build Artifacts
> ------------------------------------------------
>
>                 Key: USERGRID-758
>                 URL: https://issues.apache.org/jira/browse/USERGRID-758
>             Project: Usergrid
>          Issue Type: Story
>            Reporter: Jeffrey 
>            Assignee: David Johnson
>
> We should include in the WAR manifests a version number to be able to 
> identify a version of a build and which branch it belongs to.  For example, 
> right now we have 1.0, 2.0 and 2.1 branches and nothing about the artifact 
> filenames differentiates them.  This results to mistakes and builds of the 
> wrong version getting deployed and mistaken.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to