Maven 3.9.12 - release notes

[slawekjaranowski]

Following this checklist to help us incorporate your
contribution quickly and easily:

• Your pull request should address just one issue, without pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
  Note that commits might be squashed by a maintainer on merge.
• Run mvn site and examine output in target/site directory.
  Site will also be built on your pull request automatically and attached to GitHub Action result.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
• In any other case, please file an Apache Individual Contributor License Agreement.

[Bukama]

Reviewed as of now, ping me, when the open TODOs were filled / the release is done (I've read your mail about 3.9.12 plans).

[elharo]

I think – is wrong. This should be an em dash if it's a dash at all, though I suspect maybe a dash shouldn't be used here. DuckDuckGo LLM says"Use an em dash (—) to set off extra information or indicate a break in a sentence, while an en dash (–) is typically used to represent ranges, such as dates or numbers. The em dash is longer and can replace commas or parentheses, whereas the en dash is shorter and often signifies "to" in ranges."

[michael-o]

It depends on the style, APA, Chicago, etc. There is no caonical reference. Don't change a single file without changing the rest.

[elharo]

Requiring things to change everywhere is common meta mistake, and I specifically disagree. It is better to do the wrong thing 19 times and the right thing once than doing the wrong thing 20 times. Nor is it required or even a good idea to fix the other 19 mistakes to avoid introducing the 20th here.

[bmarwell]

I agree with @elharo here. Let's start using the correct dashes from now an, does not hurt if old release notes are different.

[elharo]

Let's remove this. I know we say it everywhere, but it's really techno-gibberish.

[elharo]

Requiring things to change everywhere is common meta mistake, and I specifically disagree. It is better to do the wrong thing 19 times and the right thing once than doing the wrong thing 20 times. Nor is it required or even a good idea to fix the other 19 mistakes to avoid introducing the 20th here.