<!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 8818 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 199, Issue 15<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. String Freeze Notice (Arthur)<br> 2. Long-term support version of Koha (bug 31008) (David Nind)<br> 3. Effective circulation rule preview/tester<br> (dcook@prosentient.com.au)<br> 4. Re: Long-term support version of Koha (bug 31008) (Paul Poulain)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 21 Jun 2022 12:13:43 +0200<br>From: Arthur <arthur.suzuki@biblibre.com><br>To: koha-devel@lists.koha-community.org<br>Subject: [Koha-devel] String Freeze Notice<br>Message-ID: <a355126e-c220-b4f6-0ebb-0fdeb7af0505@biblibre.com><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>String freeze will go into effect as of today for 21.11.x branch.<br><br>Maintenance release scheduled for the 23.<br><br>Arthur<br><br><br>------------------------------<br><br>Message: 2<br>Date: Wed, 22 Jun 2022 11:44:05 +1200<br>From: David Nind <david@davidnind.com><br>To: koha-devel@lists.koha-community.org<br>Subject: [Koha-devel] Long-term support version of Koha (bug 31008)<br>Message-ID:<br> <CAKCb+YptQ12gqUKF9stPm8fwFyionhot5aVpXyr6wMtPW2FfVg@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>At the Development IRC meeting on 8 June 2022 the issue of having a<br>long-term support version of Koha (Koha LTS) was discussed. (It has been<br>discussed and proposed in the past.)<br><br>Summary<br>=======<br><br>General agreement was reached that:<br><br>1. A long-term support (LTS) version of Koha would be for 2.5 to 3 years<br><br>2. We would start with oldstable (which is now 21.11)<br><br>3. There would be an LTS maintainer role for each cycle (there is no<br>expectation that this is the same person for up to three years - it is<br>preferable that it is someone different each cycle)<br><br>4. The mandate for the LTS version would cover:<br> . security fixes<br> . things that are broken (such as APIs (external), dependencies (such<br>as Elasticsearch), etc), and<br> . essential back ports only, once past oldoldstable<br><br>5. It would be an irregular release - only when something is needed once<br>past oldoldstable<br><br>6. We would inform the Koha Community about the LTS version of Koha, what<br>it is, and what it means for support (including updates to the website,<br>mailing list, manual section on supported versions, etc)<br><br>Next steps<br>========<br><br>Your feedback is welcome on the proposed LTS version of Koha. Feel free to<br>provide this however you wish, including replying to this email, IRC, and<br>on bug 31008.<br><br>It will then be discussed again, and the approach confirmed at the next<br>available Development IRC Meeting (ideally this would have been the 22 June<br>2022 meeting, but I've just sent this email!).<br><br>References<br>=========<br>[1] Bug 31008:<br>https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31008<br>[2] 8 June 2022 Development IRC meeting:<br> . Minutes:<br>https://meetings.koha-community.org/2022/development_irc_meeting_8_june_2022.2022-06-08-20.59.html<br> . Log:<br>https://meetings.koha-community.org/2022/development_irc_meeting_8_june_2022.2022-06-08-20.59.log.html#l-134<br><br>David Nind | david@davidnind.com<br>New Zealand<br>m. +64 21 0537 847<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220622/da500ca7/attachment-0001.htm><br><br>------------------------------<br><br>Message: 3<br>Date: Wed, 22 Jun 2022 12:16:19 +1000<br>From: <dcook@prosentient.com.au><br>To: "'koha-devel'" <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Effective circulation rule preview/tester<br>Message-ID: <023b01d885de$12f723d0$38e56b70$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all,<br><br> <br><br>How good would it be if there were a preview/tester for effective<br>circulation rules in the Admin module?<br><br> <br><br>I'm sure I'm not the only one who struggles to figure out what circulation<br>rule is being applied in any given scenario at times. I imagine a lot of<br>librarians could make use of it especially. <br><br> <br><br>Probably not something I would develop, but thought it was an interesting<br>idea.<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>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220622/6bb5202a/attachment-0001.htm><br><br>------------------------------<br><br>Message: 4<br>Date: Wed, 22 Jun 2022 09:47:36 +0200<br>From: Paul Poulain <paul.poulain@biblibre.com><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Long-term support version of Koha (bug<br> 31008)<br>Message-ID: <dd8074e0-8477-07f3-bc21-7f2d8ce78757@biblibre.com><br>Content-Type: text/plain; charset="utf-8"; Format="flowed"<br><br>Hello David & others,<br><br>Good thing to have a LTS, my main question is about the ecosystem around <br>Koha. For example, how to manage Koha LTS regarding <br>Debian/Ubuntu/Elastic Search/MariaDB... upgrades ? How can we be sure <br>that, in 2 years, Koha LTS will become "unmaintainable" because it <br>requires a Perl library that can't be upgraded and the underlying tool <br>(OS, search engine...) isn't maintained anymore in the compatible version ?<br><br>I hope that it's a theoretical question that will never become reality, <br>but it has to be asked I think.<br><br>Good day everyone<br><br>Le 22/06/2022 à 01:44, David Nind a écrit :<br>> At the Development IRC meeting on 8 June 2022 the issue of having a <br>> long-term support version of Koha (Koha LTS) was discussed. (It has <br>> been discussed and proposed in the past.)<br>><br>> Summary<br>> =======<br>><br>> General agreement was reached that:<br>><br>> 1. A long-term support (LTS) version of Koha would be for 2.5 to 3 years<br>><br>> 2. We would start with oldstable (which is now 21.11)<br>><br>> 3. There would be an LTS maintainer role for each cycle (there is no <br>> expectation that this is the same person for up to three years - it is <br>> preferable that it is someone different each cycle)<br>><br>> 4. The mandate for the LTS version would cover:<br>> . security fixes<br>> . things that are broken (such as APIs (external), dependencies <br>> (such as Elasticsearch), etc), and<br>> . essential back ports only, once past oldoldstable<br>><br>> 5. It would be an irregular release - only when something is needed <br>> once past oldoldstable<br>><br>> 6. We would inform the Koha Community about the LTS version of Koha, <br>> what it is, and what it means for support (including updates to the <br>> website, mailing list, manual section on supported versions, etc)<br>><br>> Next steps<br>> ========<br>><br>> Your feedback is welcome on the proposed LTS version of Koha. Feel <br>> free to provide this however you wish, including replying to this <br>> email, IRC, and on bug 31008.<br>><br>> It will then be discussed again, and the approach confirmed at the <br>> next available Development IRC Meeting (ideally this would have been <br>> the 22 June 2022 meeting, but I've just sent this email!).<br>><br>> References<br>> =========<br>> [1] Bug 31008: <br>> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31008<br>> [2] 8 June 2022 Development IRC meeting:<br>> . Minutes: <br>> https://meetings.koha-community.org/2022/development_irc_meeting_8_june_2022.2022-06-08-20.59.html<br>> . Log: <br>> https://meetings.koha-community.org/2022/development_irc_meeting_8_june_2022.2022-06-08-20.59.log.html#l-134<br>><br>> David Nind | david@davidnind.com<br>> New Zealand<br>> m. +64 21 0537 847<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>Paul Poulain, Associé-gérant / co-owner<br>BibLibre, Services en logiciels libres pour les bibliothèques<br>BibLibre, Open Source software and services for libraries<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220622/321ab1e2/attachment-0001.htm><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 199, Issue 15<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>