<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 14971 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 191, Issue 10<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Time to translate: string freeze to prepare Koha 20.05.17 has<br> begun (Victor Grousset/tuxayo)<br> 2. Re: Built-in offline circulation interface (Kyle Hall)<br> 3. Time to translate: string freeze to prepare Koha 19.11.23 has<br> begun (Wainui Witika-Park)<br> 4. Re: Built-in offline circulation interface<br> (dcook@prosentient.com.au)<br> 5. Re: Workflow improvement suggestions for security releases<br> (Jonathan Druart)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sun, 17 Oct 2021 16:25:40 +0200<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: koha-translate@lists.koha-community.org, koha-devel<br> <koha-devel@lists.koha-community.org>, Koha <Koha@lists.katipo.co.nz><br>Subject: [Koha-devel] Time to translate: string freeze to prepare Koha<br> 20.05.17 has begun<br>Message-ID: <c036440b-4f85-d8e0-36ae-7ea0970a4d09@tuxayo.net><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>Hi, saluton, hola, bonjour,<br><br>String freeze is into effect as of now for the 20.05.x maintenance branch.<br><br>This means it's the right time to head over to the translation platform:<br>https://translate.koha-community.org/projects/<br><br>Reminder: if you add or change a translation in version 20.05,<br>then you must also copy it to 20.11 and 21.05.<br>Otherwise your work will be lost for future versions.<br><br><br>Happy translating :)<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 2<br>Date: Sun, 17 Oct 2021 18:48:46 -0400<br>From: Kyle Hall <kyle.m.hall@gmail.com><br>To: Cab Vinton <bibliwho@gmail.com><br>Cc: Koha Devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Built-in offline circulation interface<br>Message-ID:<br> <CACpVHfzgKZWgoiR7Ft9-pd4bk=OfPGx-Dyb0yit0=Xm=HCwUZQ@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>The desktop application has been rocksolid for many years now! I’ve always<br>shied away from the browser based I’ll find circulations simply because if<br>something goes wrong, like the browser crashing and losing data or<br>something, there’s no way to get that data back. The offline circulation<br>desktop application writes everything to file as you perform actions so the<br>data doesn’t get lost in the event of a crash.<br><br>Kyle<br><br>On Sat, Oct 16, 2021 at 8:12 AM Cab Vinton <bibliwho@gmail.com> wrote:<br><br>> Fwiw, we'd somehow missed that there was a built-in capability/ system<br>> preference. Always assumed the utility was our only option.<br>><br>> This functionality is an important part of Koha's feature set, so +1<br>> to always having at least one up-to-date option available.<br>><br>> Cheers,<br>><br>> Cab Vinton, Director<br>> Plaistow Public Library<br>> Plaistow, NH<br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>><br>-- <br>---<br>http://www.kylehall.info<br>ByWater Solutions ( http://bywatersolutions.com )<br>Meadville Public Library ( http://www.meadvillelibrary.org )<br>Crawford County Federated Library System ( http://www.ccfls.org )<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211017/60ca4eb4/attachment-0001.htm><br><br>------------------------------<br><br>Message: 3<br>Date: Mon, 18 Oct 2021 12:51:37 +1300<br>From: Wainui Witika-Park <wainuiwitikapark@catalyst.net.nz><br>To: "Koha-translate@lists.koha-community.org"<br> <koha-translate@lists.koha-community.org>,<br> koha-devel@lists.koha-community.org<br>Subject: [Koha-devel] Time to translate: string freeze to prepare Koha<br> 19.11.23 has begun<br>Message-ID: <0098a13b-8dba-dbe2-d6d2-8e619fb9eeaf@catalyst.net.nz><br>Content-Type: text/plain; charset=utf-8<br><br>Hello,<br><br>String freeze is into effect as of now for the 19.11.x maintenance<br>branch in preparation for the 19.11.23 release.<br><br>This means it's the right time to head over to the translation platform:<br>https://translate.koha-community.org/projects/<br><br>Reminder: if you add or change a translation in version 19.11, then you<br>must also copy it to 20.05, 20.11 and 21.05. Otherwise your work will be<br>lost for future versions.<br><br>Happy translating!<br><br>Wainui Witika-Park (she/her)<br><br><br>------------------------------<br><br>Message: 4<br>Date: Mon, 18 Oct 2021 11:20:56 +1100<br>From: <dcook@prosentient.com.au><br>To: "'Kyle Hall'" <kyle.m.hall@gmail.com>, "'Cab Vinton'"<br> <bibliwho@gmail.com><br>Cc: "'Koha Devel'" <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Built-in offline circulation interface<br>Message-ID: <022901d7c3b6$05197e60$0f4c7b20$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Does that mean that you actually have a lot of people using the desktop application? Interesting!<br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Kyle Hall<br>Sent: Monday, 18 October 2021 9:49 AM<br>To: Cab Vinton <bibliwho@gmail.com><br>Cc: Koha Devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Built-in offline circulation interface<br><br> <br><br>The desktop application has been rocksolid for many years now! I’ve always shied away from the browser based I’ll find circulations simply because if something goes wrong, like the browser crashing and losing data or something, there’s no way to get that data back. The offline circulation desktop application writes everything to file as you perform actions so the data doesn’t get lost in the event of a crash.<br><br> <br><br>Kyle<br><br> <br><br>On Sat, Oct 16, 2021 at 8:12 AM Cab Vinton <bibliwho@gmail.com <mailto:bibliwho@gmail.com> > wrote:<br><br>Fwiw, we'd somehow missed that there was a built-in capability/ system<br>preference. Always assumed the utility was our only option.<br><br>This functionality is an important part of Koha's feature set, so +1<br>to always having at least one up-to-date option available.<br><br>Cheers,<br><br>Cab Vinton, Director<br>Plaistow Public Library<br>Plaistow, NH<br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> <br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br>-- <br><br>---<br><br>http://www.kylehall.info<br>ByWater Solutions ( http://bywatersolutions.com )<br>Meadville Public Library ( http://www.meadvillelibrary.org )<br>Crawford County Federated Library System ( http://www.ccfls.org )<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211018/d8fbce90/attachment-0001.htm><br><br>------------------------------<br><br>Message: 5<br>Date: Mon, 18 Oct 2021 09:26:58 +0200<br>From: Jonathan Druart <jonathan.druart@bugs.koha-community.org><br>To: Kyle Hall <kyle.m.hall@gmail.com><br>Cc: koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Workflow improvement suggestions for<br> security releases<br>Message-ID:<br> <CAJzKNY6xo9GFUx+zqFEhby-7qsMo6Cqz6aLBHnHHWYO9kDF=kA@mail.gmail.com><br>Content-Type: text/plain; charset="UTF-8"<br><br>Thanks for your reply, Kyle!<br>(And sorry for my delayed answer, your message hit the spam folder!?)<br><br>Inline replies below.<br><br>Le jeu. 7 oct. 2021 à 13:15, Kyle Hall <kyle.m.hall@gmail.com> a écrit :<br>>><br>>> 1. LTS<br>>> I think it's time to have a Long Term Support release. We noticed that<br>>> some people are still using very old versions, having a version that<br>>> is maintained several years could help them.<br>>> We could backport critical security bugs only. 4 (5?) years would be great.<br>><br>><br>> This has been proposed in the past. The general consensus at the time was that we as a community want to encourage libraries to stay on the latest versions of Koha and not to hang back on older versions.<br>> I'm not necessarily opposed, but such a role will require quite a commitment.<br><br>For 22.05, Calalyst and Wainui are offering to maintain 19.11, and<br>there is a gap as there is no candidate for 20.05.<br>So it's kind of our first LTS :)<br><br>>> 5. Apply patches<br>>> We need a script to apply the patches on the different branches,<br>>> automatically. That's an easy bit to develop and it will help us a<br>>> lot.<br>><br>><br>> I'm not sure what you mean? Do you mean something that would apply a bug's patch set to say master, stable and oldstable and report on the bug if it doesn't apply to one? Or script in qa-test-tools to do that? Something else entirely?<br><br>In the first step I was suggesting a script in the release-tools repo<br>to auto-apply a patch set on the different stable branches.<br>But then, our imagination is the limit :)<br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 191, Issue 10<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>