You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Henning Schmiedehausen (JIRA)" <ji...@apache.org> on 2018/09/07 21:12:00 UTC
[jira] [Commented] (MRELEASE-979) Support NamingPolicies to manage
Branch and Tag names
[ https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607669#comment-16607669 ]
Henning Schmiedehausen commented on MRELEASE-979:
-------------------------------------------------
This open bug is coming up on 20 months, the last release of the plugin is ready to go to pre-school soon (almost five years ago). Will there ever be another release of the release plugin (irony intended)?
> 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
> Assignee: Robert Scholte
> Priority: Major
> 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
(v7.6.3#76005)