And, some upstream majar version will be released during Debian's
release freeze. Well, how we can save those "missed release train"
releases? Just "ignore and wait 2 years" is easy to say, but if we
can introduce those in point releases with "predictable" schedule,
it would be better, IMHO.
* KDE Plasma: 5.27 - 2023-02?
* GNOME : 44 - 2023-03
Q4: Will Ruby3.2 go into bookworm?
Q1: When dpkg will support zstd compression?
Q2: More default hardening options? (See https://developers.redhat.com/blog/2018/03/21/compiler-and-linker-flags-gcc )
Q3: Does OpenSSH9.1p go into bookworm?
Q4: Will Ruby3.2 go into bookworm?
Q5: Will PHP8.2 go into bookworm?
Q6: Will Rust1.65 go into bookworm?
Q7: Will python3.11 be default in bookworm?
And, some upstream major version will be released during Debian's
release freeze. Well, how we can save those "missed release train" releases? Just "ignore and wait 2 years" is easy to say, but if we
can introduce those in point releases with "predictable" schedule,
it would be better, IMHO.
* KDE Plasma: 5.27 - 2023-02?
* GNOME : 44 - 2023-03
* etc...
Q7: Will python3.11 be default in bookworm?
And, some upstream majar version will be released during Debian's
release freeze. Well, how we can save those "missed release train"
releases? Just "ignore and wait 2 years" is easy to say, but if we
can introduce those in point releases with "predictable" schedule,
it would be better, IMHO.
* KDE Plasma: 5.27 - 2023-02?
Q3: Does OpenSSH9.1p go into bookworm?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 339 |
Nodes: | 16 (2 / 14) |
Uptime: | 00:06:40 |
Calls: | 7,466 |
Calls today: | 2 |
Files: | 12,691 |
Messages: | 5,627,862 |