AlmaLinux / AlmaLinux/wiki

Add list of current deviations from RHEL

未關閉
#474 2 則留言 0 個 reaction 已指派 1 人 已被 @sglewis09 認領 在 GitHub 檢視
enhancement
主要語言
Shell
星號
116
分支
94
平均合併
19 小時 30 分鐘
30 天內合併 PR
13

描述

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/

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。