Sorry for the late reply. I sadly have very limited time for Apache work these days.
The commit log is incidental. It would ideally have no repeated versions, but it's hardly a transgression if it does. Likewise, it's not a requirement of the ASF that our releases never skip version numbers. It would be nice if they did not, but again, it's not a serious issue. Put otherwise, logs and versions are there to serve the creation of a release. And "release" is the word we need to take seriously. We did not release 4.2. We still could. We could also move on and release 4.2.1. As long as we are clear that if we didn't get three +1 votes on a build, then it can't be called a release, and thus is not a released version. On Wed, Apr 10, 2024 at 1:04 PM Claude Brisson <cla...@renegat.net.invalid> wrote: > 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... > > Regards, > > Claude > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org > >
