On 2 May 2025 at 8:02:02 PM, Michael Osipov wrote:
> Changing such an important requirement in the RC phase isn't professional.
>
Under normal circumstances, I’d probably agree, but I do recall way, way,
way back in the early days of 4, there was talk of leaving the final
decision until the rel
Hi all,
I find this extremely disappointing and also confusing. A majority of
binding and non-binding votes opted FOR adopting Java 21. How can this
be justified with our procedures?
Here are my arguments for adopting Java 21 that seems to have been asked
for although they are imho obvious.
Personally I am opposed to changing the default to a worse format and
introduce a breaking change.
The `v` is redundant. If users want to use that we should enable a
configuration to do so (I think that exists already) but the default
should stay as is and use the project version.
On 2025-05
Hi,
Change was reverted from maven-parent
https://github.com/apache/maven-parent/pull/468
On Thu, 1 May 2025 at 22:30, Slawomir Jaranowski wrote:
>
> Hi,
>
> We introduce a short and the same template release tag name for Maven
> projects as:
>
> v@{project.version}
>
> in parent 44: https://git
Hi Matthias,
On 4.05.2025 08:57, Matthias Bünger wrote:
But due the high number of negative votes and brought up arguments, I
don't think we should ignore them but take them into consideration for
the benefit of the Maven community. Therefore I call the vote to be
non successful. We can reeval
