29 Jan 2026
Fedora People
Fedora Infrastructure Status: Updates and Reboots
29 Jan 2026 10:00pm GMT
23 Jan 2026
Fedora People
Christof Damian: Friday Links 26-03
23 Jan 2026 9:00am GMT
Remi Collet: 📝 Redis version 8.6 🎲
RPMs of Redis version 8.6 are available in the remi-modular repository for Fedora ≥ 42 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).
⚠️ Warning: this is a pre-release version not ready for production usage.
1. Installation
Packages are available in the redis:remi-8.6 module stream.
1.1. Using dnf4 on Enterprise Linux
# dnf install https://rpms.remirepo.net/enterprise/remi-release-<ver>.rpm # dnf module switch-to redis:remi-8.6/common
1.2. Using dnf5 on Fedora
# dnf install https://rpms.remirepo.net/fedora/remi-release-<ver>.rpm # dnf module reset redis # dnf module enable redis:remi-8.6 # dnf install redis --allowerasing
You may have to remove the valkey-compat-redis compatibilty package.
2. Modules
Some optional modules are also available:
- RedisBloom as redis-bloom
- RedisJSON as redis-json
- RedisTimeSeries as redis-timeseries
These packages are weak dependencies of Redis, so they are installed by default (if install_weak_deps is not disabled in the dnf configuration).
The modules are automatically loaded after installation and service (re)start.
The modules are not available for Enterprise Linux 8.
3. Future
Valkey also provides a similar set of modules, requiring some packaging changes already applied in Fedora official repository.
Redis may be proposed for unretirement and be back in the Fedora official repository, by me if I find enough motivation and energy, or by someone else.
I may also try to solve packaging issues for other modules (e.g. RediSearch). For now, module packages are very far from Packaging Guidelines, so obviously not ready for a review.
4. Statistics
redis
redis-bloom
redis-json
redis-timeseries
23 Jan 2026 7:28am GMT
22 Jan 2026
Fedora People
Fedora Badges: New badge: CentOS Connect 2026 Attendee !
22 Jan 2026 10:40am GMT
Fedora Badges: New badge: DevConf India 2026 Attendee !
22 Jan 2026 5:58am GMT
21 Jan 2026
Fedora People
Evgeni Golov: Validating cloud-init configs without being root
21 Jan 2026 7:42pm GMT
Fedora Infrastructure Status: dl.fedoraproject.org slow
21 Jan 2026 12:00pm GMT
Ben Cotton: Use your labels
Most modern issue trackers offer a label mechanism (sometimes called "tags" or a similar name) that allow you or your users to set metadata on issues and pull/merge requests. It's fun to set them up and anticipate all of the cool things you'll do. But it turns out that labels you don't use are worse than useless. As I wrote a few years ago, "adding more labels adds cognitive overhead to creating and managing issues, so you don't want to add complexity when you don't have to."
A label that you don't use just complicates the experience and doesn't give you useful information. A label that you're not consistent in using will lead to unreliable analysis data. Use your labels.
Jeff Fortin Tam highlighted one benefit to using labels: after two years of regular use in GNOME, it was easy to see nearly a thousand performance improvements because of the "Performance" label. (As of this writing, the count is over 1,200.)
How to ensure you use your labels
The problem with labels is that they're either present or they're not. If your process requires affirmatively adding labels, then you can't treat the absence of a label as significant. The label might be absent because it doesn't apply, or it might be absent because nobody remembered to apply it. By the same token, you don't want to apply all the labels up front and then remove the ones that don't apply. That's a lot of extra effort.
There are two parts of having consistent label usage. The first is having a simple and well-documented label setup. Only have the labels you need. A label that only applies to a small number of issues is probably not necessary. Clearly document what each label is for and under what conditions it should be applied.
The other part of consistent label usage is to automatically apply a "needs triage" label. Many ticket systems support doing this in a template or with an automated action. When someone triages an incoming issue, they can apply the appropriate labels and then remove the "needs triage" label. Any issue that still includes a "needs triage" label should be excluded from any analysis, since you can reasonably infer that it hasn't been appropriately labeled.
You'll still miss a few here and there, but that will help you use your labels, and that makes the labels valuable.
This post's featured photo by Angèle Kamp on Unsplash.
The post Use your labels appeared first on Duck Alignment Academy.
21 Jan 2026 12:00pm GMT
20 Jan 2026
Fedora People
Peter Czanik: Call for testing: syslog-ng 4.11 is coming
20 Jan 2026 12:44pm GMT
Vedran Miletić: Why we use reStructuredText and Sphinx static site generator for maintaining teaching materials
20 Jan 2026 12:34pm GMT
Vedran Miletić: What is the price of open-source fear, uncertainty, and doubt?
20 Jan 2026 12:34pm GMT
Vedran Miletić: On having leverage and using it for pushing open-source software adoption
20 Jan 2026 12:34pm GMT
Vedran Miletić: Mirroring free and open-source software matters
20 Jan 2026 12:34pm GMT
Vedran Miletić: Joys and pains of interdisciplinary research
20 Jan 2026 12:34pm GMT
Vedran Miletić: I am still not buying the new-open-source-friendly-Microsoft narrative
20 Jan 2026 12:34pm GMT
Vedran Miletić: AMD and the open-source community are writing history
20 Jan 2026 12:34pm GMT