Canceling the vote and dropping the release. It did not reach the
required quorum.
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
On 2024/02/21 11:54:51 Claude Brisson wrote:
> > I use this one [1] sans the part which does not apply to Velocity TLP to
> > comply with ASF release requirements. If there is a documentation for the
> > Velocity project which does not have more manual steps compared to the [1],
> > I will
I use this one [1] sans the part which does not apply to Velocity TLP to comply
with ASF release requirements. If there is a documentation for the Velocity
project which does not have more manual steps compared to the [1], I will
happily do it, but I don't want to waste my time for unnecessary
Guys, please note that the vote ends today. If you intend to vote, vote today.
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
On 2024/02/19 21:12:39 Claude Brisson wrote:
> On 19/02/2024 21:34, Michael Osipov wrote:
>
> > On 2024/02/19 20:25:45 Claude Brisson wrote:
> >> 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
> >>
It passes all my tests, and works great. Thanks.
On 18/02/2024 12:45, Michael Osipov wrote:
Hi,
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310104=12354231
Staging repo:
https://repository.apache.org/content/repositories/orgapachevelocity-1043/
On 19/02/2024 21:34, Michael Osipov wrote:
On 2024/02/19 20:25:45 Claude Brisson wrote:
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
On 2024/02/19 20:25:45 Claude Brisson wrote:
> 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
+1
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
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,
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
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
Hi,
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310104=12354231
Staging repo:
https://repository.apache.org/content/repositories/orgapachevelocity-1043/
13 matches
Mail list logo
