2.4.1 Release blogpost

[Eve00000]

preview:
https://deploy-preview-344--mixxx-website.netlify.app/news/2024-04-26-mixxx-2-4-1-released

[daschuer]

Thank you very much for this PR.
For you first website contribution we always need an avatar icon from you and an entry in pelican.py
Like @JoergAtGithub has done here: https://github.com/mixxxdj/website/pull/341/files

[daschuer]

You will find the complete list of changes here:
mixxxdj/mixxx#13169

Is it reasonable to list them all? Probably not.
Maybe we should list only a few an than link the changelog.

[daschuer]

The link will be:
https://github.com/mixxxdj/mixxx/blob/2.4.1/CHANGELOG.md

[daschuer]

Can you also take care to the pre-commit complains. It has found typos and trailing spaces.

[ronso0]

For all manual and website PRs, let's please add a preview link to the PR description as soon as CI has built it. (just did that)

[Eve00000]

OK, I'm learning.
Now I can see there are line problems, Can you tell me how I can make an enter? /n or <br> or ....

[ronso0]

Thanks, just a quick first review.

[ronso0]

This is very lengthy, I had trouble spotting the actual "news" (important fixes, changelog).
That can probably be improved by adding some formatting (headers, proper list style).

Appreciate the call for help with translations!

I'm open for "user stories" (new contributor experience) and a brief "what's going on" overview, though shouldn't these better go to a "guest post" or something?

[Eve00000]

I do understand what you mean, so the release info could be something like a twitter/x-post, all info could be in 100 characters.
"New update 2.4.1 with fixes, download at ...... "
But if we want to involve the Mixxx-ers (I want to use this term for all Mixxx-users, developers, ....) we need to give some info that is more than formal, some info that would change their idea of some geeks sitting behind a screen writing code the whole day long drinking coffee....
I think everybody can see the list imediately turning the mousewheel, but keeping them a little longer in the news with the mentioning of little stories/experiences tells a lot more than just new version ...
It connects.
And connection is what a community needs. Not just formal contact on forum/github/zulip,
we are all different but we share something that is valuable and important for us.
People want to know, so let's write about it.
'spreading the experience' and 'being proud' is important.

[ywwg]

looks good to me, thanks! someone in charge of the release can do the final merge

[Swiftb0y]

It'd be nice if this got a round of markdownlint before merge. It's not part of pre-commit

[Eve00000]

It'd be nice if this got a round of markdownlint before merge. It's not part of pre-commit

what kind of animal is a markdownlint?

[Swiftb0y]

https://github.com/DavidAnson/markdownlint-cli2 along with https://github.com/mixxxdj/mixxx/blob/67a41d9dcdb06b37f57be8e88978756140d05ff2/.markdownlint-cli2.yaml

[ronso0]

just set this to Draft so it'll be merged only after we polished the changelog, currently the categories and items don't match (at least the not the list in this PR)

[ronso0]

just set this to Draft so it'll be merged only after we polished the changelog, currently the categories and items don't match (at least the not the list in this PR)

Okay, the changelog is sorted correctly https://github.com/mixxxdj/mixxx/blob/2.4/CHANGELOG.md
The list here needs to be updated accordingly.

Shouldn't we list only the highlights here?

[Eve00000]

just set this to Draft so it'll be merged only after we polished the changelog, currently the categories and items don't match (at least the not the list in this PR)

Okay, the changelog is sorted correctly https://github.com/mixxxdj/mixxx/blob/2.4/CHANGELOG.md The list here needs to be updated accordingly.

Shouldn't we list only the highlights here?

I'll update the list and then you can select which ones need to go .... the more items users see, the more they can understand that it takes time to correct bugs and add features.

[Eve00000]

done

[daschuer]

@ronso0 and @Swiftb0y Is your review still pending? I have just clicked through the release 2.4.1

[Swiftb0y]

Good from my side now

[ronso0]

LGTM, just a minor fixup ;) whill I'll merge myself.

[daschuer]

Thanks all involved here ❤️

[ronso0]

the Download page hasn't been updated, yet
I thought we do that first, then publish the release post?

[ronso0]

tbc here https://mixxx.zulipchat.com/#narrow/stream/109171-development/topic/2.2E4.2E1.20and.202.2E5-beta.20deadline.202024-04-16.20approaching/near/437815046