I'd like to ask other fellow MIR team members some policy questions about the above:
#0 "seeded-in-ubuntu" policy: Why could this be a problem (as listed in https://wiki.ubuntu.com/MainInclusionProcess), do we need to update the wiki? #2 testing/qa requirements: Should we accept a single "superficial" autopkgtest as sufficient testing or require a test-plan for additional end-to-end testing? It compiles the library (using pkgconfig) and runs a single function, so confirms that the library builds/loads/executes. There isn't much more that we can do to tests such a library at runtime. (cf: https://bugs.debian.org/cgi- bin/bugreport.cgi?att=1;bug=1011314;filename=libldac.patch;msg=5) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973784 Title: [MIR] libldac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libldac/+bug/1973784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
