* 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).
* Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing.
Tested build can be found at ...
* [amd64] ...
* [arm64] ...
* [armhf] ...
* [ppc64el] ...
* [riscv64] not available
* [s390x] ...
* General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice
[Regression Potential]
* A minor release with a total of ? 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.a
[Impact]
* LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: /wiki.documentf oundation. org/ReleasePlan /7.5#7. 5.6_release
https:/
* Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.5 see the list of bugs fixed in the release candidates of 7.5.6 (that's a total of ? bugs): /wiki.documentf oundation. org/Releases/ 7.5.6/RC1# List_of_ fixed_bugs /wiki.documentf oundation. org/Releases/ 7.5.6/RC2# List_of_ fixed_bugs
https:/
https:/
7.5.6 RC2 is identical to the 7.5.6 release
* 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: /ci.libreoffice .org/job/ gerrit_ 75/1671/
https:/
* More information about the upstream QA testing can be found here: /wiki.documentf oundation. org/QA/ Testing/ Automated_ Tests /wiki.documentf oundation. org/Development /UITests /wiki.documentf oundation. org/QA/ Testing/ Regression_ Tests /wiki.documentf oundation. org/QA/ Testing/ Feature_ Tests
* 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. /wiki.ubuntu. com/Process/ Merges/ TestPlans/ libreoffice
Tested build can be found at ...
* [amd64] ...
* [arm64] ...
* [armhf] ...
* [ppc64el] ...
* [riscv64] not available
* [s390x] ...
* 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 ? 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.a