<!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 15019 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 14<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. Re: Roles for 22.05 open (Fridolin SOMERS)<br> 2. Re: Workflow improvement suggestions for security releases<br> (Chris Cormack)<br> 3. Re: Workflow improvement suggestions for security releases<br> (Kyle Hall)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 19 Oct 2021 08:51:44 -1000<br>From: Fridolin SOMERS <fridolin.somers@biblibre.com><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Roles for 22.05 open<br>Message-ID: <8a4a1bcd-cdce-b1aa-c9af-4711dcd661b7@biblibre.com><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Hi,<br><br>My proposal is now on the wiki, see you at the meeting.<br><br>Best regards<br><br>Le 13/10/2021 à 21:03, Jonathan Druart a écrit :<br>> The election of the 22.05 team will take place during the next general<br>> IRC meeting, on Wednesday October 20th 2021, 14:00 UTC.<br>> https://wiki.koha-community.org/wiki/General_IRC_meeting_20_October_2021<br>> <br>> There is still plenty of room available!<br>> <br>> <br>> Le mer. 29 sept. 2021 à 17:12, Jonathan Druart<br>> <jonathan.druart@bugs.koha-community.org> a écrit :<br>>><br>>> Hello everybody,<br>>><br>>> The roles for the 22.05 release cycle are now opened.<br>>> The vote will take place during one of the dev meetings in October.<br>>><br>>> https://wiki.koha-community.org/wiki/Roles_for_22.05<br>>><br>>> The description of the roles can be found at this wiki page<br>>> https://wiki.koha-community.org/wiki/Project_roles<br>>><br>>> Regards,<br>>> Jonathan<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>Fridolin SOMERS <fridolin.somers@biblibre.com><br>Software and system maintainer 🦄<br>BibLibre, France<br><br><br>------------------------------<br><br>Message: 2<br>Date: Wed, 20 Oct 2021 07:59:06 +1300<br>From: Chris Cormack <chrisc@catalyst.net.nz><br>To: koha-devel@lists.koha-community.org, Kyle Hall<br> <kyle.m.hall@gmail.com>, Jonathan Druart<br> <jonathan.druart@bugs.koha-community.org><br>Subject: Re: [Koha-devel] Workflow improvement suggestions for<br> security releases<br>Message-ID: <68B12077-805B-466F-82B4-8D88856C1E27@catalyst.net.nz><br>Content-Type: text/plain; charset="utf-8"<br><br>We have very few (I think none) 19.11 libraries left. Almost all of our libraries are either running 21.05 or in the process of upgrading). However we have committed to maintain 19.11 for the community for at least one more cycle. <br><br>It's very low maintenance as its pretty much just security patches from here.<br>If no one else takes over it next cycle we will do it again.<br><br>Having an LTS release would be useful. By far the majority of Koha libraries are not with a support provider, and if we check hea, there's a large (1000+) number of libraries running a version of 19.11.<br><br>It would also be one step closer to getting into Debian proper. (a long term dream of mine) <br><br>Chris <br><br><br><br>On 20 October 2021 7:13:39 am NZDT, Kyle Hall <kyle.m.hall@gmail.com> wrote:<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>><br>>I suppose we need to understand Catalyst's upgrade strategy a bit more. It<br>>we as a community are going to do LTS, we need to really commit to it.<br>>19.11 will be two years out as of the 21.11 release.<br>>Ubuntu LTS releases are every two years. If my math is correct, that would<br>>mean that 21.11 would be the next LTS release. Does Catalyst plan on<br>>upgrading from 19.11 to 21.11?<br>>I'm curious how many libraries would utilize an LTS release and upgrade<br>>bi-annually.<br>>Do we have any metrics on what is being pulled from the community apt<br>>server? If not, is it possible to add tracking?<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>>That sounds good to me! I can imagine a new bugzilla field for "Fails to<br>>apply to" that would be a list of release branches ( 21.05.x, 20.11.x, etc<br>>) so we would be aware.<br>><br>>Kyle<br><br>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211020/1b8354a7/attachment-0001.htm><br><br>------------------------------<br><br>Message: 3<br>Date: Tue, 19 Oct 2021 18:59:53 -0400<br>From: Kyle Hall <kyle.m.hall@gmail.com><br>To: Chris Cormack <chrisc@catalyst.net.nz><br>Cc: Koha Devel <koha-devel@lists.koha-community.org>, Jonathan Druart<br> <jonathan.druart@bugs.koha-community.org><br>Subject: Re: [Koha-devel] Workflow improvement suggestions for<br> security releases<br>Message-ID:<br> <CACpVHfy-r107_cD+9bu3PbOGp_DvPgc_2-dgSjCGnZ=qJRi=bA@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Thanks Chris!<br><br>I suppose the next question is, does a 2 year LTS cycle sound right for<br>Koha?<br><br>Kyle<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><br>On Tue, Oct 19, 2021 at 2:59 PM Chris Cormack <chrisc@catalyst.net.nz><br>wrote:<br><br>> We have very few (I think none) 19.11 libraries left. Almost all of our<br>> libraries are either running 21.05 or in the process of upgrading). However<br>> we have committed to maintain 19.11 for the community for at least one more<br>> cycle.<br>><br>> It's very low maintenance as its pretty much just security patches from<br>> here.<br>> If no one else takes over it next cycle we will do it again.<br>><br>> Having an LTS release would be useful. By far the majority of Koha<br>> libraries are not with a support provider, and if we check hea, there's a<br>> large (1000+) number of libraries running a version of 19.11.<br>><br>> It would also be one step closer to getting into Debian proper. (a long<br>> term dream of mine)<br>><br>> Chris<br>><br>><br>><br>> On 20 October 2021 7:13:39 am NZDT, Kyle Hall <kyle.m.hall@gmail.com><br>> wrote:<br>>><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>>><br>>> I suppose we need to understand Catalyst's upgrade strategy a bit more.<br>>> It we as a community are going to do LTS, we need to really commit to it.<br>>> 19.11 will be two years out as of the 21.11 release.<br>>> Ubuntu LTS releases are every two years. If my math is correct, that<br>>> would mean that 21.11 would be the next LTS release. Does Catalyst plan on<br>>> upgrading from 19.11 to 21.11?<br>>> I'm curious how many libraries would utilize an LTS release and upgrade<br>>> bi-annually.<br>>> Do we have any metrics on what is being pulled from the community apt<br>>> server? If not, is it possible to add tracking?<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>>> That sounds good to me! I can imagine a new bugzilla field for "Fails to<br>>> apply to" that would be a list of release branches ( 21.05.x, 20.11.x, etc<br>>> ) so we would be aware.<br>>><br>>> Kyle<br>>><br>> --<br>> Sent from my Android device with K-9 Mail. Please excuse my brevity.<br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211019/6dc5dd14/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 191, Issue 14<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>