Today is the day! — Nitrux 3.9.1 "mk" is available to download — https://nxos.org

We are pleased to announce the launch of Nitrux 3.9.1. This new version combines the latest software updates, bug fixes, performance improvements, and ready-to-use hardware support.

Nitrux 3.9.1 is available immediately.

Changelog: https://nxos.org/changelog/release-announcement-nitrux-3-9-1/

#changelog New Ruby versions available on 2024 architecture: 3.4.1, 3.3.7 #ruby → https://changelog.alwaysdata.com/445/detail/

#changelog New PHP versions available on 2024 architecture: 8.4.3, 8.3.16, 8.2.27 #php → https://changelog.alwaysdata.com/443/detail/

Today is the day! — Nitrux 3.9.0 "pd" is available to download — https://nxos.org

We are pleased to announce the launch of Nitrux 3.9.0. This new version combines the latest software updates, bug fixes, performance improvements, and ready-to-use hardware support.

Nitrux 3.9.0 is available immediately.

Changelog: https://nxos.org/changelog/release-announcement-nitrux-3-9-0/

Today is the day! — Nitrux 3.8.0 "db" is available to download — https://nxos.org

We are pleased to announce the launch of Nitrux 3.8.0. This new version combines the latest software updates, bug fixes, performance improvements, and ready-to-use hardware support.

Nitrux 3.8.0 is available immediately.

Changelog: https://nxos.org/changelog/release-announcement-nitrux-3-8-0/

Today is the day! — Nitrux 3.7.0 "ub" is available to download — https://nxos.org

We are pleased to announce the launch of Nitrux 3.7.0. This new version combines the latest software updates, bug fixes, performance improvements, and ready-to-use hardware support.

Nitrux 3.7.0 is available immediately.

Changelog: https://nxos.org/changelog/release-announcement-nitrux-3-7-0/

#documentation #releases #changelog #git #tickets

"Summary: We'd all benefit from restoring the distinction between a detailed changelog and brief release notes, but that's hard to do if a project relies solely on GitHub as its communication platform"

- https://harihareswara.net/posts/2024/changelogs-and-release-notes/

- https://hachyderm.io/@nedbat/113152493265812268

- https://docs.oscollective.org/guides/marketing-publicity-roadmaps-and-comms

Thanks @brainwane !

"How should you generate changelogs?

The audience for your commit history and your changelog are very distinct from each other. These different audiences care about different things. Any changelog system based on extracting commit messages is therefore doomed to fail."

https://sophiabits.com/blog/conventional-changelogs-suck

Ich mag ja kreative #Changelog​s mit einem Hang zur selbstkritischen Ironie. Hier aktuell von #Tidal:

„We chased down some bugs, including one particularly elusive crash issue. We’re pretty sure it’s gone, but if it reappears, we'll act surprised.“

Ich erinnere mich auch an abenteuerlich lustige Changelogs der VW-App „WeShare“ (die es allerdings nicht mehr gibt).

Habt ihr auch (positive) Beispiele?

This has most likely gone unnoticed, but I've updated the design of https://hasty.dev, this is mostly just the header and footer to match some of the new features I'd like to implement fully at some point in the future - time is valuable

Also, half way down the landing-page, I've added direct links to various sorting algorithm comparisons. I (of course) highly encourage y'all to check them out

Ps. @hasty.dev now has it's own account

#hasty #changelog
That's all for now. Thanks

Calling all #changelog afficionados!

I've released an alpha and a series of betas of something, and soon I will be releasing a non-beta, which will have few or no changes (compared to the latest beta).

So when a user reads through the changelog they now need to read through 7 beta versions of changes to see accumulated changes since the last non-beta release. The first alpha has most of the new features listed. Seems silly.

How do you manage this? Links to good examples welcome, thanks! :)

Changelog 2023-26 – a summer christmas

https://press.ash.ms/2023/12/26/changelog-2023-26-a-summer-christmas/

I'm excited to announce that the new version of **git-cliff** is out!

A highly customizable Changelog Generator - written in Rust.

GitHub: https://github.com/orhun/git-cliff

Release highlights: https://git-cliff.org/blog/1.4.0

While we are getting ready for the 3.24 "Prizren" release (named after the #foss4g2023 host city), feel free to kick back and get inspired by our new visual #changelog:
https://www.youtube.com/watch?v=LHFVo0edaXE

challenge accepted, #changelog

Today is the day! — Nitrux 3.0.0 "ut" is available to download

We are pleased to announce the launch of Nitrux 3.0.0. This new version combines the latest software updates, bug fixes, performance improvements, and ready-to-use hardware support.

Nitrux 3.0.0 is available immediately.

https://nxos.org/changelog/release-announcement-nitrux-3-0-0/

Simple HTTP and REST Server Update
Version 1.2 Changelog

- Handle cors requests in simple event server script
- Fix nullable warning in HttpListenerRequestExtension.cs
- Fix file id confilcts with other shadow grove files

https://assetstore.unity.com/packages/tools/utilities/simple-http-and-rest-server-244127?utm_source=mastedon

Gleich zweimal "#WTF #RHEL?" heute:

Ja, nee, is' klar:

#rpm -q --changelog kernel | egrep '^\*' | awk '{print $5}' | uniq
2022
2021
2020
2019
2018
2023
2022
2021
2020
2019
2018
2023
2022
2021
2020
2019
2018

Seit wann sind #Changelogs nimmer chronologisch sortiert und die neusten #Changelog-Einträge kommen irgendwo mittendrin in dem Wust?

Und wieso hat https://access.redhat.com/errata/RHSA-2023:1566 korrekt englischsprachige Überschriften, https://access.redhat.com/errata/RHSA-2023:1569 aber (bis auf "CVE") chinesische Überschriften?