[
https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895215#comment-15895215
]
Henning Schmiedehausen commented on MRELEASE-979:
-------------------------------------------------
I knew you were going to say that. Ok, let me send a pull request for the
*other* branch that I have that has exactly this change in it.
Once this went in, how are the chances of getting a 3.0.0 release soon (I have
a number of people here waiting on an official release with all changes merged)
The #15 pull request above does exactly what [~rfscholte] was suggesting
(splitting config settings for tag names (prepare goal) and branches (branch
goal).
Please consider merging this change; I tested it with our internal code bases
and that would fulfil what we need. Also, once this is in, getting a 3.0.0
release would be fantastic.
> Support NamingPolicies 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)
