[jira] [Commented] (MRELEASE-979) Allow VersionPolicies to manage Branch and Tag names

["Henning Schmiedehausen (JIRA)" <ji...@apache.org>]

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

Henning Schmiedehausen commented on MRELEASE-979:
-------------------------------------------------

pretty ping? :-) [~rfscholte] is the second implementation (pull #12) along what you were thinking? I would love to get this in before a 3.0.0 release; this change makes it possible for us to codify our branch and tag strategy in code and use this across the organization. 

> 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.15#6346)