> > Hi, i'm TLP's upstream/author. > Hello, glad to hear from you which implies that you have an eye on these issues as well - that is great.
> I do shellchecks for every TLP release (there even is a Makefile target > for it) but didn't re-check with 20.04 before the 1.3 release. My bad. Feel > free to make use of my commit: > [...] Yes I have seen that none are critical which is why I have put it to the optional list of things to look at. [...] I can say without immodesty that TLP itself breaks very rarely. > That is great to hear (well, not for the kernel) but great still for TLP itself. Overall you relieve some of my concerns about code complexity with these statements. But those were not stopping this process anyway. Thanks for your feedback linrunner! @Linrunner - one more question for you - do you also have access to a test matrix of different HW systems e.g. to test a new release on many different HW/Kernel combos? Sounds like overkill in terms of space/power/money requirement, but you know - in a perfect world - such a thing would exist. Seeing you here I thought I might ask. In General, still what is missing here for promotion is a team subscriber, I'll ask around in todays MIR meeting if one team planned to own it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888656 Title: [MIR] tlp To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1888656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
