Release Maintainer for 3.2 Proposal

3.2 represents a significant advancement in the number and quality of features offered by Koha. With the valuable investment of both time and money in this growth by members of the community, the responsibility and stewardship of vigilant maintenance devolves upon the community. With that in mind, I propose the following:

• that the 3.2 Release Maintainer become the point of convergence of the several maintenance efforts outlined below.
• that regular consultation and coordination with the current Release Manager and Translation Manager be an integral part of the work of the Release Maintainer.
• that a regular schedule of maintenance releases be published and maintained.
• that after the next two subsequent stable releases of Koha, the developers meet and decide on an end-of-support (EOS) date for 3.2. By announcing and maintaining both a schedule of maintenance and, eventually, an EOS date, Koha support vendors, their customers, and the user community at large will be able to better plan their maintenance and migration schedules.

Release once every 30 days or as bug fixes are available whichever is longer.

Release once very 90 days or as bug fixes are available whichever is longer.

Meet with developer's to decide on an EOS date. Release twice more: once mid-way to EOS and once at EOS.

With this growth will come the undesirable but inevitable appearance of bugs. The fixes for such bugs should be applied to the current development HEAD and back-ported to the 3.2 codebase.

The ever increasing exposure and usage of Koha across the world will lead to the need of updating and expanding the languages into which Koha is translated. This expansion should be part of the maintenance process in order to help enlarge the user base of Koha.

Undoubtedly there will appear from time to time enhancements of the current 3.2 feature set which it will be desirable to implement into the 3.2 code base. While it is not the purpose of 3.2 to morph into a semi-3.4 release, there should be some room for improvement. The regular maintenance release of 3.2 should include such items as appropriate.