| 2022-06-03 13:59:26 |
Rico Tzschichholz |
bug |
|
|
added bug |
| 2022-06-03 13:59:33 |
Rico Tzschichholz |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-06-03 13:59:33 |
Rico Tzschichholz |
bug task added |
|
libreoffice (Ubuntu Jammy) |
|
| 2022-06-03 13:59:40 |
Rico Tzschichholz |
libreoffice (Ubuntu): status |
New |
Fix Released |
|
| 2022-06-03 13:59:43 |
Rico Tzschichholz |
libreoffice (Ubuntu Jammy): status |
New |
In Progress |
|
| 2022-06-03 13:59:44 |
Rico Tzschichholz |
libreoffice (Ubuntu Jammy): importance |
Undecided |
High |
|
| 2022-06-03 13:59:46 |
Rico Tzschichholz |
libreoffice (Ubuntu Jammy): assignee |
|
Rico Tzschichholz (ricotz) |
|
| 2022-06-04 07:19:07 |
Rico Tzschichholz |
description |
[Impact]
* LibreOffice 7.3.4 is in its forth bugfix release of the 7.3 line:
https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.4_release
* Version 7.3.3 is currently released in jammy. For a list of fixed bugs compared to 7.3.3 see the list of bugs fixed in the release candidates of 7.3.4 (that's a total of ?? bugs):
https://wiki.documentfoundation.org/Releases/7.3.4/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/7.3.4/RC2#List_of_fixed_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]
* 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://ci.libreoffice.org/job/gerrit_73/1599/
* More information about the upstream QA testing can be found here:
* Automated tests
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
* Automated UI tests
https://wiki.documentfoundation.org/Development/UITests
* Regression tests
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
* Feature tests
https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
* Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing.
* [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 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 7.3.4 is in its forth bugfix release of the 7.3 line:
https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.4_release
* Version 7.3.3 is currently released in jammy. For a list of fixed bugs compared to 7.3.3 see the list of bugs fixed in the release candidates of 7.3.4 (that's a total of ?? bugs):
https://wiki.documentfoundation.org/Releases/7.3.4/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/7.3.4/RC2#List_of_fixed_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]
* 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://ci.libreoffice.org/job/gerrit_73/1599/
* More information about the upstream QA testing can be found here:
* Automated tests
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
* Automated UI tests
https://wiki.documentfoundation.org/Development/UITests
* Regression tests
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
* Feature tests
https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
* Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing.
* [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220603_201544_36a8d@/log.gz
* [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220603_204754_3736d@/log.gz
* [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220603_200320_e5429@/log.gz
* [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220603_173801_fcc50@/log.gz
* [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220603_165906_4db31@/log.gz
* 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. |
|
| 2022-06-10 14:09:13 |
Timo Aaltonen |
libreoffice (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2022-06-10 14:09:14 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-06-10 14:09:15 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2022-06-10 14:09:17 |
Timo Aaltonen |
tags |
|
verification-needed verification-needed-jammy |
|
| 2022-06-16 11:26:57 |
Rico Tzschichholz |
tags |
verification-needed verification-needed-jammy |
verification-done verification-done-jammy |
|
| 2022-06-16 14:43:04 |
Rico Tzschichholz |
description |
[Impact]
* LibreOffice 7.3.4 is in its forth bugfix release of the 7.3 line:
https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.4_release
* Version 7.3.3 is currently released in jammy. For a list of fixed bugs compared to 7.3.3 see the list of bugs fixed in the release candidates of 7.3.4 (that's a total of ?? bugs):
https://wiki.documentfoundation.org/Releases/7.3.4/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/7.3.4/RC2#List_of_fixed_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]
* 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://ci.libreoffice.org/job/gerrit_73/1599/
* More information about the upstream QA testing can be found here:
* Automated tests
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
* Automated UI tests
https://wiki.documentfoundation.org/Development/UITests
* Regression tests
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
* Feature tests
https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
* Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing.
* [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220603_201544_36a8d@/log.gz
* [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220603_204754_3736d@/log.gz
* [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220603_200320_e5429@/log.gz
* [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220603_173801_fcc50@/log.gz
* [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220603_165906_4db31@/log.gz
* 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. |
[Impact]
* LibreOffice 7.3.4 is in its forth bugfix release of the 7.3 line:
https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.4_release
* Version 7.3.3 is currently released in jammy. For a list of fixed bugs compared to 7.3.3 see the list of bugs fixed in the release candidates of 7.3.4 (that's a total of 88 bugs):
https://wiki.documentfoundation.org/Releases/7.3.4/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/7.3.4/RC2#List_of_fixed_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]
* 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://ci.libreoffice.org/job/gerrit_73/1599/
* More information about the upstream QA testing can be found here:
* Automated tests
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
* Automated UI tests
https://wiki.documentfoundation.org/Development/UITests
* Regression tests
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
* Feature tests
https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
* Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing.
* [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220603_201544_36a8d@/log.gz
* [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220603_204754_3736d@/log.gz
* [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220603_200320_e5429@/log.gz
* [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220603_173801_fcc50@/log.gz
* [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220603_165906_4db31@/log.gz
* 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 88 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. |
|
| 2022-06-21 20:09:10 |
Launchpad Janitor |
libreoffice (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2022-06-21 20:09:35 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
