[
https://issues.apache.org/jira/browse/VELOCITY-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18034779#comment-18034779
]
Claude Brisson commented on VELOCITY-990:
-----------------------------------------
We had a [related discussion on the dev
list|https://lists.apache.org/thread/yvllhbhqszof2c740nxcs7bpppdgprks] last
year.
Release candidates *may* become published releases, but if they do, they cannot
be changed. So it seems that the only correct way to have the scm show the
final version number (if that is of some importance, because after all they
point to the correct sources) would to delete tags of failed RCs, but as
[~michaelo] recalled, this can also be problematic.
Or, as an alternative, we would, if the vote for an RC succeeds, allow to
re-publish the almost same artifact but with the final versioned tag, which
would require a second vote... this is not reasonable.
So having the scm/tag indicate the last RC is the lesser of two evils. Listing
tags will show that there is no further RC for the release. Can you elaborate
why it is a problem?
> Releasing: make sure that scm/tag in pom.xml matches git tag
> ------------------------------------------------------------
>
> Key: VELOCITY-990
> URL: https://issues.apache.org/jira/browse/VELOCITY-990
> Project: Velocity
> Issue Type: Task
> Reporter: Peter Palaga
> Priority: Major
>
> Hi, I noticed the following issue on recent releases that were preceded by
> RCs:
> The scm/tag is the RC version, not the actually released version that is
> present in <version> and that would match git tag.
> For example, for release 2.4.1, the tag and versions in pom.xml files are all
> {{2.4.1}}, but the scm/tag is
> {code:xml}
> <scm>
> ...
> <tag>2.4.1-rc1</tag>
> </scm>
> {code}
> Could you please adjust your processes next time, to make rebuilds easier?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
