* 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.
* A minor release with a total of ?? bug fixes always carries the potential for introducing regressions, even though it is a bug-fix-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.
[Impact]
* LibreOffice 6.4.7.2.M1 is a bug-fix release of the 6.4 line: /blog.documentf oundation. org/blog/ 2013/06/ 17/the- document- foundation- welcomes- frances- mimo-in- the-advisory- board/)
It receives important bug-fixes on top of the 6.4 branch which is EOL since November 30, 2020. Currently maintained by Andras Timar for France's MIMO (https:/
* Version 6.4.7 is currently released in focal. /cgit.freedeskt op.org/ libreoffice/ core/log/ ?h=distro/ mimo/mimo- 6-4
https:/
(that's a total of ?? bugs)
* 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]
* Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. /launchpad. net/~ricotz/ +archive/ ubuntu/ ppa/+sourcepub/ 12419370/ +listing- archive- extra
https:/
* [amd64] ...
* [arm64] ...
* [armhf] ...
* [ppc64el] ...
* [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 bug-fix-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.