| 2019-07-16 14:40:02 |
Marcus Tomlinson |
bug |
|
|
added bug |
| 2019-07-16 14:40:51 |
Marcus Tomlinson |
bug task added |
|
libreoffice-l10n (Ubuntu) |
|
| 2019-07-16 14:40:55 |
Marcus Tomlinson |
libreoffice-l10n (Ubuntu): assignee |
|
Marcus Tomlinson (marcustomlinson) |
|
| 2019-07-16 14:40:57 |
Marcus Tomlinson |
libreoffice (Ubuntu): assignee |
|
Marcus Tomlinson (marcustomlinson) |
|
| 2019-07-16 14:40:59 |
Marcus Tomlinson |
libreoffice (Ubuntu): importance |
Undecided |
High |
|
| 2019-07-16 14:41:01 |
Marcus Tomlinson |
libreoffice-l10n (Ubuntu): importance |
Undecided |
High |
|
| 2019-07-16 14:41:10 |
Marcus Tomlinson |
nominated for series |
|
Ubuntu Disco |
|
| 2019-07-16 14:41:10 |
Marcus Tomlinson |
bug task added |
|
libreoffice (Ubuntu Disco) |
|
| 2019-07-16 14:41:10 |
Marcus Tomlinson |
bug task added |
|
libreoffice-l10n (Ubuntu Disco) |
|
| 2019-07-16 14:41:15 |
Marcus Tomlinson |
libreoffice (Ubuntu Disco): assignee |
|
Marcus Tomlinson (marcustomlinson) |
|
| 2019-07-16 14:41:16 |
Marcus Tomlinson |
libreoffice-l10n (Ubuntu Disco): assignee |
|
Marcus Tomlinson (marcustomlinson) |
|
| 2019-07-16 14:41:18 |
Marcus Tomlinson |
libreoffice (Ubuntu Disco): importance |
Undecided |
High |
|
| 2019-07-16 14:41:19 |
Marcus Tomlinson |
libreoffice-l10n (Ubuntu Disco): importance |
Undecided |
High |
|
| 2019-07-16 15:07:10 |
Marcus Tomlinson |
description |
[Impact]
* LibreOffice 6.2.5 is in its fifth bugfix release of the 6.2 line. Version 6.2.5 is currently in Eoan.
For a list of fixed bugs compared to 6.2.4 see the list of bugs fixed in the two release candidates:
https://wiki.documentfoundation.org/Releases/6.2.5/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/6.2.5/RC2#List_of_fixed_bugs
(that's a total of 118 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 118 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.2.5 is in its fifth bugfix release of the 6.2 line. Version 6.2.5 is currently in Eoan.
For a list of fixed bugs compared to 6.2.4 see the list of bugs fixed in the two release candidates:
https://wiki.documentfoundation.org/Releases/6.2.5/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/6.2.5/RC2#List_of_fixed_bugs
https://www.libreoffice.org/about-us/security/advisories/cve-2019-9848/
https://www.libreoffice.org/about-us/security/advisories/cve-2019-9849/
(that's a total of 120 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 120 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. |
|
| 2019-07-16 15:08:48 |
Marcus Tomlinson |
description |
[Impact]
* LibreOffice 6.2.5 is in its fifth bugfix release of the 6.2 line. Version 6.2.5 is currently in Eoan.
For a list of fixed bugs compared to 6.2.4 see the list of bugs fixed in the two release candidates:
https://wiki.documentfoundation.org/Releases/6.2.5/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/6.2.5/RC2#List_of_fixed_bugs
https://www.libreoffice.org/about-us/security/advisories/cve-2019-9848/
https://www.libreoffice.org/about-us/security/advisories/cve-2019-9849/
(that's a total of 120 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 120 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.2.5 is in its fifth bugfix release of the 6.2 line. Version 6.2.5 is currently in Eoan.
For a list of fixed bugs compared to 6.2.4 see:
https://wiki.documentfoundation.org/Releases/6.2.5/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/6.2.5/RC2#List_of_fixed_bugs
https://www.libreoffice.org/about-us/security/advisories/cve-2019-9848/
https://www.libreoffice.org/about-us/security/advisories/cve-2019-9849/
(that's a total of 120 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 120 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. |
|
| 2019-07-16 21:56:42 |
Marcus Tomlinson |
description |
[Impact]
* LibreOffice 6.2.5 is in its fifth bugfix release of the 6.2 line. Version 6.2.5 is currently in Eoan.
For a list of fixed bugs compared to 6.2.4 see:
https://wiki.documentfoundation.org/Releases/6.2.5/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/6.2.5/RC2#List_of_fixed_bugs
https://www.libreoffice.org/about-us/security/advisories/cve-2019-9848/
https://www.libreoffice.org/about-us/security/advisories/cve-2019-9849/
(that's a total of 120 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 120 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.2.5 is in its fifth bugfix release of the 6.2 line. Version 6.2.5 is currently in Eoan.
For a list of fixed bugs compared to 6.2.4 see:
https://wiki.documentfoundation.org/Releases/6.2.5/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/6.2.5/RC2#List_of_fixed_bugs
(that's a total of 118 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 118 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. |
|
| 2019-07-17 17:49:56 |
Marcus Tomlinson |
libreoffice-l10n (Ubuntu Disco): status |
New |
In Progress |
|
| 2019-07-17 17:49:59 |
Marcus Tomlinson |
libreoffice-l10n (Ubuntu): status |
New |
In Progress |
|
| 2019-07-17 17:50:00 |
Marcus Tomlinson |
libreoffice (Ubuntu Disco): status |
New |
In Progress |
|
| 2019-07-17 17:50:03 |
Marcus Tomlinson |
libreoffice (Ubuntu): status |
New |
In Progress |
|
| 2019-07-17 18:11:11 |
Launchpad Janitor |
libreoffice-l10n (Ubuntu Disco): status |
In Progress |
Fix Released |
|
| 2019-07-17 18:11:11 |
Launchpad Janitor |
cve linked |
|
2019-9848 |
|
| 2019-07-17 18:11:11 |
Launchpad Janitor |
cve linked |
|
2019-9849 |
|
| 2019-07-17 18:11:28 |
Launchpad Janitor |
libreoffice (Ubuntu Disco): status |
In Progress |
Fix Released |
|
| 2019-07-17 18:39:51 |
Marcus Tomlinson |
libreoffice-l10n (Ubuntu): status |
In Progress |
Fix Released |
|
| 2019-07-17 18:39:53 |
Marcus Tomlinson |
libreoffice (Ubuntu): status |
In Progress |
Fix Released |
|
