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

Michael Osipov commented on MRELEASE-1073:
------------------------------------------

bq. I want to make major releases from trunk, like 1.0, 1.1... for which the 
corresponding SNAPSHOTS are 1.0-SNAPSHOT, 1.1-SNAPSHOT... and minor release 
like 1.0.0, 1.0.1, 

This is wrong. You are confusing what major and minor releases are. Please read 
semver.org.

bq. being able to change the version in the maintenance branch, to the proper 
minor version, during the release process.

This works

bq. being able to generate properly numbered "beta" version, which could maybe 
be similar to the release process, but with 'beta' or'-beta' before the last 
digit version. 

This works are you initially provided {{-beta-1}} qualifier.

> 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
>
>         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.1#820001)

Reply via email to