Hello David & others,
Good thing to have a LTS, my main question is about the ecosystem around
Koha. For example, how to manage Koha LTS regarding
Debian/Ubuntu/Elastic Search/MariaDB... upgrades ? How can we be sure
that, in 2 years, Koha LTS will become "unmaintainable" because it
requires a Perl library that can't be upgraded and the underlying tool
(OS, search engine...) isn't maintained anymore in the compatible version ?
I hope that it's a theoretical question that will never become reality,
but it has to be asked I think.
Good day everyone
Le 22/06/2022 à 01:44, David Nind a écrit :
At the Development IRC meeting on 8 June 2022 the issue of having a
long-term support version of Koha (Koha LTS) was discussed. (It has
been discussed and proposed in the past.)
Summary
=======
General agreement was reached that:
1. A long-term support (LTS) version of Koha would be for 2.5 to 3 years
2. We would start with oldstable (which is now 21.11)
3. There would be an LTS maintainer role for each cycle (there is no
expectation that this is the same person for up to three years - it is
preferable that it is someone different each cycle)
4. The mandate for the LTS version would cover:
. security fixes
. things that are broken (such as APIs (external), dependencies
(such as Elasticsearch), etc), and
. essential back ports only, once past oldoldstable
5. It would be an irregular release - only when something is needed
once past oldoldstable
6. We would inform the Koha Community about the LTS version of Koha,
what it is, and what it means for support (including updates to the
website, mailing list, manual section on supported versions, etc)
Next steps
========
Your feedback is welcome on the proposed LTS version of Koha. Feel
free to provide this however you wish, including replying to this
email, IRC, and on bug 31008.
It will then be discussed again, and the approach confirmed at the
next available Development IRC Meeting (ideally this would have been
the 22 June 2022 meeting, but I've just sent this email!).
References
=========
[1] Bug 31008:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31008
[2] 8 June 2022 Development IRC meeting:
. Minutes:
https://meetings.koha-community.org/2022/development_irc_meeting_8_june_2022.2022-06-08-20.59.html
. Log:
https://meetings.koha-community.org/2022/development_irc_meeting_8_june_2022.2022-06-08-20.59.log.html#l-134
David Nind | da...@davidnind.com
New Zealand
m. +64 21 0537 847
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website :https://www.koha-community.org/
git :https://git.koha-community.org/
bugs :https://bugs.koha-community.org/
--
Paul Poulain, Associé-gérant / co-owner
BibLibre, Services en logiciels libres pour les bibliothèques
BibLibre, Open Source software and services for libraries
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/
