[MRELEASE-431] Configuration of policy for calculating next (release) version

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta-8
• Fix Version/s: 2.5.1
• Component/s: prepare
• Assignee: Robert Scholte
• Reporter: Carsten Ziegeler
• Created: 28/Mar/09 10:27
• Updated: 09/Mar/23 07:12
• Resolved: 17/Mar/18 10:21

Description

Currently, when preparing the release, the version to release is always the next version which usually is the current version without the snapshot extension.
There are quite a lot of projects (Apache Felix, Sling and others) following an even release numbering policy. So while the current development version is odd (like 1.2.3-SNAPSHOT), the next released version will be 1.2.4.
It would be nice if this could be made configuration through some configuration property like
<versionPolicy>next-even</versionPolicy> (with possible values being: next (default, as-is), next-even, next-odd

I briefly scanned through the code and it seems that adding support for this requires changes in both, the release-manager and the release-plugin.

If this feature gets accepted and if someone could give me some minor hints how/where to add this I could come up with a patch.

Issue Links

• is depended upon by: MRELEASE-1078 Support version policy to read and use SCM tags and commits
• is depended upon by: MRELEASE-793 Release version hinting - stripping SNAPSHOT with unsupported versioning
• is duplicated by: MRELEASE-797 support semantic versioning
• supercedes: MRELEASE-550 Version incrementation in non interactive release (batch-mode / -B)
• links to: GitHub Pull Request #169