Am 2024-04-10 um 22:01 schrieb Claude Brisson:
Hi team.
Can we clarify a little bit the versioning for the future releases?
My point of view is quite simple: did the engine 4.2 get released? No.
So it should be the next version. If it's not what is intended, I need a
detailed explanation, because I really don't understand Michael response:
> because that version should not appear more than once on the log:
https://github.com/apache/velocity-engine/commits/master/.
What do you mean exactly by the fact that a "version" does "appear" on
the "log"? None of those terms are clear to me in this context...
Claude,
the Git log contains the messages from the Maven Release Plugin with
that tag name chosen during release time. E.g., "[maven-release-plugin]
prepare release 2.4.1" from [1].
Yet another point I'd like to raise is that the should keep manual steps
to a minimum. Avoid gaps in the sequence just creates even more friction
in the release process. Looking at [2], way too complex.
At the end the only viable releases are the source tarball and what
people will download from Maven Central.
Michael
[1]
https://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#scmReleaseCommitComment
[2] https://velocity.apache.org/release-process.html
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
