Opened 9 months ago
Closed 9 months ago
#19967 closed enhancement (fixed)
systemd-256.1
| Reported by: | Bruce Dubbs | Owned by: | Douglas R. Reno |
|---|---|---|---|
| Priority: | normal | Milestone: | 12.2 |
| Component: | BOOK | Version: | git |
| Severity: | normal | Keywords: | |
| Cc: |
Description ¶
New minor version.
Change History (8)
follow-ups: 2 4 comment:1 by , 9 months ago
comment:2 by , 9 months ago
Replying to Xi Ruoyao:
Hmm do we take systemd point releases now? We generally didn't do that before...
I just added the ticket because currency picked it up. Waiting for the next major version will certainly help with the workload. In the last 16 weeks we've had over 1000 commits...
comment:3 by , 9 months ago
| Owner: | changed from to |
|---|
follow-up: 5 comment:4 by , 9 months ago
Replying to Xi Ruoyao:
Hmm do we take systemd point releases now? We generally didn't do that before...
I can't be sure but it appears starting with 256.0 that the systemd/systemd-stable/tags branch is no longer being used. 256.1 and 256.2 have come out on the systemd/systemd/releases/ path. These would have been on systemd-stable previously.
There was some justification to put up 256.1 as a special case because a way to accidentally delete your /home directory was reported.
It would be consistent with what you were doing to put the point releases in "wait for next major release" status. On the other hand you've been choosing to put energy into backporting patches for things that were fixed in the point releases. Makes no difference to me as I have been updating with the systemd-stable point releases for some years.
comment:5 by , 9 months ago
Replying to martyj19:
It would be consistent with what you were doing to put the point releases in "wait for next major release" status.
"Wait for ..." is an ad-hoc thing. I.e. if generally we should update to any new version, but this new version is particularly useless for us (or any Linux system, or whatever) we add this. If generally we should only update to new major version we reprogram the script checking the new versions.
comment:6 by , 9 months ago
| Status: | new → assigned |
|---|
comment:7 by , 9 months ago
I think for the future the best approach will be to monitor these releases for security implications or critical bugs, but otherwise ignore them until major releases.
This particular update is extremely important though, so I'll sync it with LFS sometime today or tomorrow.
comment:8 by , 9 months ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Hmm do we take systemd point releases now? We generally didn't do that before...