[Koha-devel] Workflow improvement suggestions for security releases

[Kyle Hall]

Thanks Chris!

I suppose the next question is, does a 2 year LTS cycle sound right for
Koha?

Kyle
---
http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )


On Tue, Oct 19, 2021 at 2:59 PM Chris Cormack <chrisc at catalyst.net.nz>
wrote:

> 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.
>
> It's very low maintenance as its pretty much just security patches from
> here.
> If no one else takes over it next cycle we will do it again.
>
> 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.
>
> It would also be one step closer to getting into Debian proper. (a long
> term dream of mine)
>
> Chris
>
>
>
> On 20 October 2021 7:13:39 am NZDT, Kyle Hall <kyle.m.hall at gmail.com>
> wrote:
>>
>>
>> For 22.05, Calalyst and Wainui are offering to maintain 19.11, and
>>> there is a gap as there is no candidate for 20.05.
>>> So it's kind of our first LTS :)
>>>
>>
>> I suppose we need to understand Catalyst's upgrade strategy a bit more.
>> It we as a community are going to do LTS, we need to really commit to it.
>> 19.11 will be two years out as of the 21.11 release.
>> Ubuntu LTS releases are every two years. If my math is correct, that
>> would mean that 21.11 would be the next LTS release. Does Catalyst plan on
>> upgrading from 19.11 to 21.11?
>> I'm curious how many libraries would utilize an LTS release and upgrade
>> bi-annually.
>> Do we have any metrics on what is being pulled from the community apt
>> server? If not, is it possible to add tracking?
>>
>> In the first step I was suggesting a script in the release-tools repo
>>> to auto-apply a patch set on the different stable branches.
>>> But then, our imagination is the limit :)
>>>
>>
>> That sounds good to me! I can imagine a new bugzilla field for "Fails to
>> apply to" that would be a list of release branches ( 21.05.x, 20.11.x, etc
>> ) so we would be aware.
>>
>> Kyle
>>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211019/6dc5dd14/attachment.htm>