** Description changed: [IMPACT] The sos team is pleased to announce the release of sos-4.3. This release includes a number of quality-of-life changes to both end user experience and for contributors dealing with the plugin API. [TEST PLAN] Documentation for Special Cases: https://wiki.ubuntu.com/SosreportUpdates - [WHERE PROBLEM COULD OCCUR] + [WHERE PROBLEMD COULD OCCUR] Regression could occur at core functionality, which may prevent sos (or its subcommand to work. I consider this regression type as 'low'. That is generally well tested, and we would find a problem at an early stage during the verification phase if it is the case. On the other end, regression could happen and are some kind of expected at plugins levels. As of today, sos has more than 300 plugins. It is nearly impossible to test them all. If a regression is found in a plugin, it is rarely affecting sos core functionalities nor other plugins. So mainly the impact would be limited to that plugin. The impact being that the plugin can't or partially can collect the information that it is instructed to gather. A 3rd party vendor would then ask user/customer to collect the information manually for that particular plugins. Plugins are segmented by services and/or applications (e.g. openstack_keystone, bcache, system, logs, ...) in order to collect things accordingly to the plugin detected or intentionally requested for. Sosreport plugins philosophy is to (as much as possible) maintain backward compatibility when updating a plugin. The risk that an ancient version of a software has been dropped, is unlikely, unless it was intended to be that way for particular reasons. Certain plugin also support the DEB installation way and the snap one (MAAS, LXD, ...) so all Ubuntu standard installation types are covered. * Problem found and fixed during the packaging process: ** sos-help module wasn't part of the build process ** sos-help man page wasn't also not part of the build process nor mention in main sos man page Bug: https://github.com/sosreport/sos/issues/2860 Both commits of PR need to be part of 4.3 Ubuntu package: https://github.com/sosreport/sos/pull/2861 Known issue: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1962733 [OTHER INFORMATION] Release note: https://github.com/sosreport/sos/releases/tag/4.3
** Description changed: [IMPACT] The sos team is pleased to announce the release of sos-4.3. This release includes a number of quality-of-life changes to both end user experience and for contributors dealing with the plugin API. [TEST PLAN] Documentation for Special Cases: https://wiki.ubuntu.com/SosreportUpdates - [WHERE PROBLEMD COULD OCCUR] + [WHERE PROBLEMS COULD OCCUR] Regression could occur at core functionality, which may prevent sos (or its subcommand to work. I consider this regression type as 'low'. That is generally well tested, and we would find a problem at an early stage during the verification phase if it is the case. On the other end, regression could happen and are some kind of expected at plugins levels. As of today, sos has more than 300 plugins. It is nearly impossible to test them all. If a regression is found in a plugin, it is rarely affecting sos core functionalities nor other plugins. So mainly the impact would be limited to that plugin. The impact being that the plugin can't or partially can collect the information that it is instructed to gather. A 3rd party vendor would then ask user/customer to collect the information manually for that particular plugins. Plugins are segmented by services and/or applications (e.g. openstack_keystone, bcache, system, logs, ...) in order to collect things accordingly to the plugin detected or intentionally requested for. Sosreport plugins philosophy is to (as much as possible) maintain backward compatibility when updating a plugin. The risk that an ancient version of a software has been dropped, is unlikely, unless it was intended to be that way for particular reasons. Certain plugin also support the DEB installation way and the snap one (MAAS, LXD, ...) so all Ubuntu standard installation types are covered. * Problem found and fixed during the packaging process: ** sos-help module wasn't part of the build process ** sos-help man page wasn't also not part of the build process nor mention in main sos man page Bug: https://github.com/sosreport/sos/issues/2860 Both commits of PR need to be part of 4.3 Ubuntu package: https://github.com/sosreport/sos/pull/2861 Known issue: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1962733 [OTHER INFORMATION] Release note: https://github.com/sosreport/sos/releases/tag/4.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960996 Title: [sru] sos upstream 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
