User:Victor Grousset - tuxayo/Community work/Reports/2022-02

Release maintenance of 20.11.x branch

Backport list: 14

• Bug 29696 - "Suggest for purchase" missing biblio link
• Bug 29018 - Deleting patrons from REST API doesn't do any checks or move to deletedborrowers
• Bug 28926 - Update cpanfile for Mojolicious::Plugin::OpenAPI v2.16
• Bug 29736 - Error when placing a hold for a club without members
• Bug 29457 - Fee Cancellation records the wrong manager_id
• Bug 27793 - Store Contents of FTX segment of EDI quotes for inclusion in orders
• Bug 29670 - Restore functionality broken by bug 27708 for AcqCreateItem set to "placing an order"
• Bug 28932 - Backend overriding status_graph element causes duplicate actions
• Bug 28832 - [21.05] Batch modification always clears permanent_location if it is mapped in frameworks
• Bug 29495 - Issue link is lost in return claims when using 'MarkLostItemsAsReturned'
• Bug 30045 - SCO print slip is broken
• Bug 29722 - Add some diversity to sample quotes
• Bug 29862 - TestBuilder.t fails with ES enabled
• Bug 29881 - Remove SQLite2 dependency

Minor stuff

Patchsets analyzed but not backported: 54

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, quick analysis
• missing dependencies/not affecting my branch
• not enough benefits compared to the risks of regression

Backport attempts: 3

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

• Issue with upstream backport, reported: Bug 29457 - Fee Cancellation records the wrong manager_id
• Bug 29804 - Koha::Hold->is_pickup_location_valid explodes if empty list of pickup locations
• Bug 29808 - Stock rotation fails to advance when an item is checked out from the branch that is the next stage

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.

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.

New tickets opened

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