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... . Log: https://meetings.koha-community.org/2022/development_irc_meeting_8_june_2022... David Nind | david@davidnind.com New Zealand m. +64 21 0537 847