[Koha-devel] Workflow improvement suggestions for security releases

[Kyle Hall]

> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211019/82d20196/attachment.htm>