[SRU] libreoffice 7.3.6 for jammy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libreoffice (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
Rico Tzschichholz |
Bug Description
[Impact]
* LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line:
https:/
* Version 7.3.5 is currently released in jammy. For a list of fixed bugs compared to 7.3.5 see the list of bugs fixed in the release candidates of 7.3.6 (that's a total of 50 bugs):
https:/
https:/
* Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes.
[Testing]
* Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually).
* A recent set of upstream's automated jenkins testing can be found here:
https:/
* More information about the upstream QA testing can be found here:
* Automated tests
https:/
* Automated UI tests
https:/
* Regression tests
https:/
* Feature tests
https:/
* Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing.
* [amd64] https:/
* [arm64] https:/
* [armhf] https:/
* [ppc64el] https:/
* [s390x] https:/
* General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https:/
[Regression Potential]
* A minor release with a total of 50 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed.
* A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in.
Changed in libreoffice (Ubuntu): | |
status: | New → Fix Released |
Changed in libreoffice (Ubuntu Jammy): | |
status: | New → In Progress |
assignee: | nobody → Rico Tzschichholz (ricotz) |
importance: | Undecided → High |
description: | updated |
While reviewing, I see that a new `libreoffice- common. preinst. in` maintscript has been added. The script itself seems to be sane, but can we add a test case to the test plan that would test the scenario of the preinst? Making sure that it works and also that it doesn't actually remove anything invalidly. Thanks!