* 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.
[Test Case]
* No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates.
* The libreoffice packages include autopkgtests, those should be run and verified to pass.
* General smoke testing of all the applications in the office suite should be carried out.
[Regression Potential]
* A minor release with a total of nnn 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.
[Impact]
* LibreOffice 6.0.7 is the seventh bugfix release of the fresh 6.0 line. Version 6.0.6 is currently in bionic. /wiki.documentf oundation. org/Releases/ 6.0.7/RC1# List_of_ fixed_bugs /wiki.documentf oundation. org/Releases/ 6.0.7/RC2# List_of_ fixed_bugs
For a list of fixed bugs compared to 6.0.6 see the list of bugs fixed in the two release candidates:
https:/
https:/
(that's a total of nnn 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.
[Test Case]
* No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates.
* The libreoffice packages include autopkgtests, those should be run and verified to pass.
* General smoke testing of all the applications in the office suite should be carried out.
[Regression Potential]
* A minor release with a total of nnn 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.