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

Robert Scholte commented on MRELEASE-979:
-----------------------------------------

First step is to introduce a new policy in the release-api, e.g. 
{{o.a.m.s.release.policy.name.NamePolicy}} (or label?). Introduce a matching 
Request. I'm still in doubt a tag and a branch follow the same policy, probably 
not. In that case you should think of 2 separate implementations.

> 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