User:Victor Grousset - tuxayo/Community work/Reports/2021-03

Release maintenance of 19.11.x branch

Backport list: 10

• Bug 27569 - marc-framework import function doesn't accept LibreOffice csv/ods file formats
• Bug 26997 - Database Mysql Version 8.0.22 failed to Update During Upgrade
• Follow up of Bug 26592 - XSS vulnerability when ysearch is used
• Bug 27626 - Patron self-registration breaks if categorycode and password are hidden
• Bug 24398 - Error when viewing single news item and NewsAuthorDisplay pref set to OPAC
• Bug 27821 - sanitize_zero_date does not handle datetime
• Bug 27798 - Independent branches should have a warning
• Bug 27784 - Unknown authority types break elasticsearch authorities indexing
• Bug 26457 - DB DeadLock when renewing checkout items
• Bug 27933 - Order patron search broken (dateofbirth, cardnumber, expirationdate)

Minor stuff

Patchsets analyzed but not backported: 31

This plus the backported patches gives and idea of the stream of patches to process.

Not backported due to one of the following:

• severity too low considering this is the oldoldstable branch of Koha
• missing dependencies/not affecting my branch
• not enough benefits compared to the risks of regression

Backport attempts: 4

Some time needed to determine whether it impacts 19.11 or the feasibility of the backport. And also attempts to backport not possible due to code conflicts.

• Bug 26208 - Overdues restrictions not consistently removed when renewing multiple items at once (edit)
• Bug 26457 - DB DeadLock when renewing checkout items
• Bug 27808 - Item's onloan column remains unset if a checked out item is issued to another patron without being returned first
• Bug 27597 - Searching "kw:term" does not work with Elasticsearch

QA

Notes:

• An attempt results in feedback provided on the bug. To ask if I correctly followed the test plan due to results that I couldn't interpret. Or if there is indeed an issue.
• Partial QA is a way to contribute to a ticket that I can't QA alone but for which I can apply the test plan and run the QA script. Leaving the functional or code review for someone knowing that area.

Began analysis of 1 patchsets

Often one must start reviewing a patch and test plan to really know if it's possible or not to QA it. This is still a way to get to know more Koha and the code though. And eventually find issues.

Signoffs (testing submitted patches so they can move on to be integrated)

Note: an attempt usually results in feedback provided on the bug. To ask if I correctly followed the test plan due to results that I couldn't interpret. Or if there is indeed an issue.

Misc tasks and work on tickets: Analysis or implementation

Tried to troubleshoot "reset_all_unimarc is not working correctly"

https://gitlab.com/koha-community/koha-testing-docker/-/issues/223

Documentation

Created a page with questions and answers about the translation process

https://wiki.koha-community.org/wiki/Traduction_Koha

New tickets opened

i.e. Found something wrong and documented how to reproduce it. Or suggest an enhancement (usually for dev tools)

Reported issue with sandboxes

https://github.com/bywatersolutions/koha-sandboxes-docker/issues/47