- Koha-devel - lists.koha-community.org

Automatic Renewal Digests not working in 21.05.03
by dcook＠prosentient.com.au 22 Oct '21

22 Oct '21

Hi all, Has anyone got Automatic Renewal Digests to work? I've looked at the code and at a glance it looks fine in 21.05.03, but emails aren't going out when Digests are selected. Emails go out fine without the Digests selected. Before I dig into the guts of it, I figured I'd ask if anyone else has had this problem. Cheers, David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Workflow improvement suggestions for security releases
by Jonathan Druart 20 Oct '21

20 Oct '21

Hello devs, As you must know we had two hard months, several very bad bugs hit us. The release team had to coordinate and it was not an easy task. We noticed some flaws in the workflow and I would like to suggest some improvements to discuss. The main problematic issue is to backport patch series to different stable branches. 1. LTS I think it's time to have a Long Term Support release. We noticed that some people are still using very old versions, having a version that is maintained several years could help them. We could backport critical security bugs only. 4 (5?) years would be great. 2. Communication Once the issues have been reported and fixed, I've alerted the first cycle of people around me. Their job was to alert a second cycle. Should we have a list of people we trust? Ask the (general) mailing list who wants to be in the loop? That means adding them to the security group on bugzilla (or at least adding them when the bug has a fix) and CC them when private discussions take place. 3. Synchronisation Release maintainers are spread around the world (and timezones suck). Getting feedback can take time, several days (like: "try", "don't work", "try again", it's 3 days!). Then when you plan to release on Wednesday, and things are only ready on Thursday you need to wait until Monday as part of the world is still enjoying the weekend! I don't have a solution for that, apart from the Monday postpone or... more anticipation. Same problem for the time of the release, I've picked 12 UTC as the "most convenient" slot for a release, but it won't (ofc) fit everybody's needs. My point was that if we communicated enough beforehand (but not publicly) it should not be a problem. Let me know if you have ideas to improve that! 4. Infrastructure improvement We don't have CI/Jenkins for the security repository. We need one! That must be a top priority of the next cycle. We need to help RMaints and make the security release process easier and less stressful. 5. Apply patches We need a script to apply the patches on the different branches, automatically. That's an easy bit to develop and it will help us a lot. 6. More visibility on the status of the patches RM and RMaints must put their progress on the bug report itself. A comment "Will be pushed, RM had a look at this" or "Backported for..." should be added. That must be added to the "Release process" wiki page. Let us know if you have any questions or remarks. Cheers, Jonathan

3 5

Roles for 22.05 open
by Jonathan Druart 19 Oct '21

19 Oct '21

Hello everybody, The roles for the 22.05 release cycle are now opened. The vote will take place during one of the dev meetings in October. https://wiki.koha-community.org/wiki/Roles_for_22.05 The description of the roles can be found at this wiki page https://wiki.koha-community.org/wiki/Project_roles Regards, Jonathan

2 2

Built-in offline circulation interface
by Owen Leonard 19 Oct '21

19 Oct '21

Does anyone use it? The one enabled by the AllowOfflineCirculation system preference. I don't think the core functionality of the feature has been touched since its original introduction and I'm concerned that it either doesn't work or is too fragile to be used in production. I'm not asking because I'm thinking of using it but because I'm concerned about us promising users that it works. Thanks, Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org

6 9

Changing the lost card value
by Stephen Graham 18 Oct '21

18 Oct '21

Sorry if this is a basic question. I've searched through the Koha::Patron and C4::Members perldoc and had a quick look through the memberentry.pl code to see how this handles it, but I can't seem to work out how it done. I want to change the value of the lost card field to zero. I can see the "lost" field in the borrowers table, so could update the value directly via SQL, but there must be a Koha method that I can use to do this? Any help/advice much appreciated! Cheers, Stephen -------------------------------------- Stephen Graham Library Technology Consultant Library and Computing Services University of Hertfordshire Hatfield, Hertfordshire, AL10 9AB Tel: +44(0)1707 286111 Ext: 77751 Email: s.graham4(a)herts.ac.uk<mailto:s.graham4@herts.ac.uk> Website: herts.ac.uk

4 6

Time to translate: string freeze to prepare Koha 19.11.23 has begun
by Wainui Witika-Park 18 Oct '21

18 Oct '21

Hello, String freeze is into effect as of now for the 19.11.x maintenance branch in preparation for the 19.11.23 release. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 19.11, then you must also copy it to 20.05, 20.11 and 21.05. Otherwise your work will be lost for future versions. Happy translating! Wainui Witika-Park (she/her)

1 0

Time to translate: string freeze to prepare Koha 20.05.17 has begun
by Victor Grousset/tuxayo 17 Oct '21

17 Oct '21

Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 20.05.x maintenance branch. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.05, then you must also copy it to 20.11 and 21.05. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo

1 0

Time to translate: string freeze to prepare 20.11.11 release
by Fridolin SOMERS 16 Oct '21

16 Oct '21

Hi, String freeze is into effect 🥶 The 20.11.x maintenance branch is preparing for 20.11.11 release 📦 This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Keep in mind that translations must be done with priority on higher version 21.05 🔥 Happy translating 🌎🌍🌏 -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 0

Call for news - Newsletter October 2021
by Koha Newsletter 13 Oct '21

13 Oct '21

Hi I'm collecting news for the October 2021 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

Issues fetching from Koha Git due to Let's Encrypt root certificate expiry
by dcook＠prosentient.com.au 08 Oct '21

08 Oct '21

Hi all, Some people might have found they aren't able to fetch from the Koha Git (in koha-testing-docker for instance). They might be getting the following error: fatal: unable to access 'https://git.koha-community.org/Koha-community/Koha.git/': server certificate verification failed. CAfile: none CRLfile: none That seems to be due to the Let's Encrypt root certificate expiry. I imagine the latest koha-testing-docker probably doesn't have this problem, but if you're lazy or time poor like me, you can just run the following to get your existing koha-testing-docker to work again: apt-get update apt-get install ca-certificates Cheers, David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 1