Bug#950488: buster-pu: package kronosnet/1.8-2
Control: tags -1 + moreinfo
Apologies for not replying sooner.
On Sun, 2020-02-02 at 14:47 +0100, Ferenc Wágner wrote:
> I'v got a bold request: please let me update Kronosnet in buster from
> 1.8-2 to 1.13-something to fix #946222. During the buster freeze
> period, upstream released 1.9 and 1.10, but those didn't bring
> important
> fixes, so I didn't request freeze exceptions for them. However, when
> Proxmox VE 6.0 got released (based on Debian buster), their users
> reported lots of intertwined bugs, and the developers iterated
> through
> 1.11, 1.12 and 1.13 in quick succession to fix them, see the linked
> https://forum.proxmox.com/threads/pve-5-4-11-corosync-3-x-major-issues.56124.
Do upstream have a stable or LTS tree? I see that unstable currently
contains 1.15, so 1.X is presumably not it.
Usually when considering a larger update, we'd be looking for
information such as:
- What sort of changes get included in upstream releases? Are they just
bug fixes, or are there new features included, or other changes?
- What sort of testing do the new releases get? Is the testing
automated?
- What sort of regressions are reported against new releases? How
quickly are they resolved?
Regards,
Adam
Reply to: