You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/12/25 22:46:00 UTC
[jira] [Updated] (MRELEASE-1073) Pre-Release generation
[ https://issues.apache.org/jira/browse/MRELEASE-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MRELEASE-1073:
-------------------------------------
Fix Version/s: wontfix-candidate
> Pre-Release generation
> ----------------------
>
> Key: MRELEASE-1073
> URL: https://issues.apache.org/jira/browse/MRELEASE-1073
> Project: Maven Release Plugin
> Issue Type: New Feature
> Reporter: Stéphane Passignat
> Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
> Attachments: image-2022-01-02-22-54-58-570.png, image-2022-01-03-12-10-55-213.png, image-2022-01-03-12-13-06-345.png, image-2022-01-03-12-14-20-084.png
>
>
> Before generating a final release, it's often required to publish several kind of beta version. When one is validated, it's intended to become a pure release.
> SCM aspect:
> * create a tag
> * create a branch (option)
> Process impact:
> * be able to generate a release from a tag or revision
> * be able to generate a pre-release from a tag or revision
> Version number:
> * the version is calculated looking at the scm tags (ex: 1.0-SNAPSHOT become 1.0.beta14 if the tags matching the tag pattern have as higher number 1.0.beta13)
>
>
> There are maybe some discussion about the version number. Should it be .beta or -beta...
>
> I think it would be great to have this feature in the release plugin, keeping in one consistent tool all release facets.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)