I was re-checking all open tasks to see if we'd be ready by now TL;DR - details below
required: - #1 halfdone: apparmor added, but not upstreamed (or not documented where it was done) - #2 done: updated to latest version (and now there is 4.4 and asks for that, but that is OK next time) - #3 open: how to run semi-automated test/checkbox - #4 open: documentation - #5 open: submit delta - #bonus: do we still want to MIR this or did we go other directions recommended: - #2 open: build time testing - #7 open: open issues --- required #1 add isolation bug 2083458 added apparmor rules. But they are not yet submitted upstream for discussion and might thereby drift away from their evolution I asked about it in that bug. Furthermore there seem to be related ntpsec changes needed to allow reading which Graham opened there. So in regard to #1 we are done if we reduce it to the pure "was isolation added". But the ecosystem and long term maintenance is still a bit rough. --- required #6 Please merge the latest version That was done, we are on 4.2 There now is 4.4 which I've heard some asking for, but this shall not be an infinite spinwheel. New versions would be merged about once every 6 months once it is in main and part of normal maintenance. If you want or need to bump it in advance, feel free to do so. --- recommended #2 build time tests Still missing, was that discussed with upstream if there is "no way" or if something would be possible and coming? --- recommended #3 how to do the tests with special HW or checkbox? Not yet answered Can this be run in testflinger or is it yet another infra we`d need to know? Given our increased focus on ensuring maintainability and documentation I'm also bumping this up to a mandatory requirement - not from the MIR rules, but in the context of the deal that the server team will continue maintenance of this for the future. --- recommended #4 usage documentation Not yet added Given our increased focus on ensuring maintainability and documentation I'm also bumping this up to a mandatory requirement - not from the MIR rules, but in the context of the deal that the server team will continue maintenance of this for the future. --- recommended #5 submit delta to upstream I've not yet seen referenced to that being done. And I realized I asked about the same again in the context of the apparmor rules above. Given our increased focus on ensuring maintainability and documentation I'm also bumping this up to a mandatory requirement - not from the MIR rules, but in the context of the deal that the server team will continue maintenance of this for the future. --- recommended #7 open bugs None of those have been addressed yet, neither in Ubuntu nor in Debian nor upstream AFAICS. --- required #Bonus - do we want linuxptp, or statime or none in main? On statime vs linuxptp - so far this isn't a clear cut case. I have the team behind this MIR that gladly already had a look, but telling me that so far: "... is far from replacing LinuxPTP. Their focus is on a PTP library implementation, and the provided daemon is currently very limited compared to LinuxPTP’s suite of applications" And then I see [1] which says "both are as good". Those two statements are not mutually exclusive, statime might so far be after ptp protocol and linuxptp has more extra things - I'll schedule a mid-cycle discussion to find what we or our peers want from linuxptp as I need to understand that. But for now that means linuxppt it is as outlined by the requesting team. While the industrial team did a lot we asked for they also have created a snap and are considering that to be sufficient for their use case - not yet fully decided. So we need to find what use-cases we need to cover and how we resolve that before we add it to main without being clear if and for what it is supposed to continue to work. [1]: https://tweedegolf.nl/en/blog/129/statime-vs-linux-ptp-comparison- of-precision --- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071717 Title: [MIR] linuxptp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linuxptp/+bug/2071717/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
