AlmaLinux / AlmaLinux/wiki

Add list of current deviations from RHEL

Open
#474 2 comments 0 reactions 1 assignee Claimed by @sglewis09 View on GitHub
enhancement
Dominant language
Shell
Stars
116
Forks
94
Avg merge
19h 30m
Merged PRs (30d)
13

Description

Since we are loud about when we deviate from RHEL, and not loud about when we re-sync with RHEL, our community is gaining the understanding that we are more widely deviated from RHEL than we are. I know that https://wiki.almalinux.org/development/Modified-packages.html exists, but that doesn't track ongoing deviations, and when they are resolved.

I would like to see a table added either to that page or another page that shows very clearly when and where we deviated, and a brief mention of why, along with when the deviation resolved itself. As an example:

| Package or service | Date of release (production) | reason for deviation (with link) | OS Version impacted | Date deviation was resolved (with link) |
| --- | --- | --- | --- |--- |
| glibc | Aug 8th, 2024 | regression bug ([blog](https://almalinux.org/blog/2024-07-25-testing-glibc-needed/)) | Almalinux 9.4 | not yet resolved |
| openSSH | July 1st, 2024 | root exploit ([blog](https://almalinux.org/blog/2024-07-01-almalinux-9-cve-2024-6387/)) | Almalinux 9 | |

In this table, the link should either be to the PR where we merged the change in, or to a blog post or whatever, if we made one.

Examples of things we should be including in this table (and the full list that I have):
https://almalinux.org/blog/zenbleed-patch-call-for-testing/
https://almalinux.org/blog/testers-needed-for-updated-packages-intel-and-amd-cpus-affected/
https://almalinux.org/blog/2024-04-02-xz-and-cve-2024-1086/
https://almalinux.org/blog/2024-07-01-almalinux-9-cve-2024-6387/
https://almalinux.org/blog/2024-07-09-cve-2024-6409/
https://almalinux.org/blog/2024-07-25-testing-glibc-needed/

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.