[
https://issues.apache.org/jira/browse/MRELEASE-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17467933#comment-17467933
]
Stéphane Passignat edited comment on MRELEASE-1073 at 1/3/22, 11:48 AM:
------------------------------------------------------------------------
Thanks Michael,
I actually run this process on several applications and libraries and would
like to make it stronger, while migrating some apps from svn to git. It
actually uses shell scripts to run which is kind of painful, only runs on
linux, ... while the SCM and version API of the plugin here are great.
*About the release process*
I use the branch feature to create the maintenance branch. So in trunk I have
1.0-SNAPSHOT producing 1.0 artifacts and update version to 1.1-SNAPSHOT...
In the generated (maintenance) branch I would like to generate 1.0.0, 1.0.1
patch version but the version is still 1.0-SNAPSHOT. Then when I release from
this branch (without paying attention) I generate a 1.1 version which can
override the 1.1 version in the artifact repository produced from the trunk.
So it would be great to change the version in the generated branch or to have
an option to generate a patch branch with the version properly modified.
!image-2022-01-03-12-14-20-084.png!
* In red what (we) want to achieve
* In green what's currently happening
*About beta process.*
What do you mean by _'Tag from beta isn't a problem. Works straight away.'_ ?
This can be done in this plugin ? or does this already exists ?
was (Author: JIRAUSER281033):
Thanks Michael,
I actually run this process on several applications and libraries and would
like to make it stronger, while migrating some apps from svn to git, as it
actually uses shell scripts to run which is kind of painful, only runs on
linux, ... while the SCM and version API of the plugin here are great.
*About the release process*
I use the branch feature to create the maintenance branch. So in trunk I have
1.0-SNAPSHOT producing 1.0 artifacts and update version to 1.1-SNAPSHOT...
In the generated (maintenance) branch I would like to generate 1.0.0, 1.0.1
patch version but the version is still 1.0-SNAPSHOT. Then when I release from
this branch (without paying attention) I generate a 1.1 version which can
override the 1.1 version in the artifact repository produced from the trunk.
So it would be great to change the version in the generated branch or to have
an option to generate a patch branch with the version properly modified.
!image-2022-01-03-12-14-20-084.png!
* In red what (we) want to achieve
* In green what's currently happening
*About beta process.*
What do you mean by _'Tag from beta isn't a problem. Works straight away.'_ ?
This can be done in this plugin ? or does this already exists ?
> 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)
