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

ASF GitHub Bot commented on MRELEASE-979:
-----------------------------------------

GitHub user hgschmie opened a pull request:

    https://github.com/apache/maven-release/pull/11

    MRELEASE-979: Allow VersionPolicies to manage Branch and Tag names

    Adds a new method to the VersionPolicy interface to allow
    configuration of Branch and Tag names in a version policy.

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

    $ git pull https://github.com/hgschmie/maven-release MRELEASE-979

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

    https://github.com/apache/maven-release/pull/11.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 #11
    
----
commit 00be62111fd7fb1f1b46a79558fd9a20d5756bc6
Author: Henning Schmiedehausen <[email protected]>
Date:   2017-01-25T01:13:05Z

    implements MRELEASE-979: Allow VersionPolicies to manage Branch and Tag 
names
    
    Adds a new method to the VersionPolicy interface to allow
    configuration of Branch and Tag names in a version policy.

----


> Allow VersionPolicies to manage Branch and Tag names
> ----------------------------------------------------
>
>                 Key: MRELEASE-979
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-979
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>          Components: branch, prepare, update-versions
>    Affects Versions: 2.5.3
>            Reporter: Henning Schmiedehausen
>             Fix For: 3.0.0
>
>
> The newly introduced VersionPolicy facility allows managing the development 
> and release versions of projects when releasing, branching and updating 
> versions.
> Most organizations will also have a policy around how branches and tags are 
> named (which often have to match specific versioning patterns). The current 
> VersionPolicy implementations do not allow this but it should be possible.



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

Reply via email to