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 2017/01/25 01:15:26 UTC

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

     [ https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henning Schmiedehausen updated MRELEASE-979:
--------------------------------------------
    Summary: Allow VersionPolicies to manage Branch and Tag names  (was: Allow ReleasePolicies to manage Branch and Tag names)

> 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 ReleasePolicy 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 ReleasePolicy implementations do not allow this but it should be possible.



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