Version numbers are advertized and are supposed to be coherent. We don't care that the tags are public, they are not advertized. I didn't say that you had to reuse the tag. The tag can be named 2.4-RC2. You don't have to rename anything, or did I miss something?

  Claude

On 18/02/2024 23:06, Michael Osipov wrote:
There are several issues with reusing tags and why this is wrong:

* Versions are cheap
* As soon as a tag is pushed it is replicated (public), changing the tag would 
break public
* Git log would show the same version twice on master: does not make sense
* Building the two tags with the same version would yield a different result
* Fiddling in the repo to rename something is unnecessary manual work for me
* Failed version is marked as archived, visible that it didn't make it

It Maven land we simply burn version because it is honest and straight forward. 
Doing additional manual steps for tens of components does not really work.

Michael

On 2024/02/18 15:28:11 Claude Brisson wrote:
The previous "2.4" was just a PR, so why would we jump to 2.4.1 for the
version ? It's a minor annoyance if you cannot reuse the tag 2.4, just
name the tag 2.4-final or something like that, no? It's more annoying if
there is a phantom 2.4 version number which has not been release, IMO.

On 18/02/2024 13:45, Michael Osipov wrote:
Hi,

Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310104&version=12354231

Staging repo:
https://repository.apache.org/content/repositories/orgapachevelocity-1043/

https://repository.apache.org/content/repositories/orgapachevelocity-1043/org/apache/velocity/velocity-engine-parent/2.4.1/velocity-engine-parent-2.4.1-source-release.zip


Source release checksum(s):
velocity-engine-parent-2.4.1-source-release.zip
sha512:
140854cf8e2a1f315b954d8be8c56f0087a13ec647065ecdea3594d2cb0099414fede608a2a9392f15beb04e6fb89b220710d0032b9bd734113e6bf578550187

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org

Reply via email to