Koha Development
How to Start the Process
- Submit a ticket to ByWater Solutions with your workflow or idea.
- ByWater Solutions will communicate to the partner, providing options for what we think the development would look like. You can read more about our mission and philosophy with Custom Development.
- We ask you if you would like a quote for the custom development.
- If you say yes, we take that idea or workflow to an internal ByWater Solutions Meeting, DevRev, or Development Review. At the meeting, we have a conversation about the idea or workflow. We ask the group if it serve the needs of the community.
- ByWater Solutions then supplies a formal quote of what the development will cost. From there, the library can decide if they want to fund it alone, or we can put it on the Development Crowdsourcing.
Koha Community Development Cycle
The Koha community uses Bugzilla to track bugs and enhancements, and every piece of code follows a standard path to production.
Under the release schedule on the Koha Community Website, there is a complete breakdown of how code gets into Koha.
When is my bug going to be fixed?
It’s upgrade time, and you’ve run into a problem in Koha. You’ve sent us a detailed ticket with screenshots, examples, and a desperate plea for a speedy resolution. The Support team has told you that you’ve encountered a known bug (or maybe you’ve discovered a new one!), and sends you a link to a site called Bugzilla. What the heck are you supposed to do with that? Why can’t ByWater fix your problem right now?
Koha is an open-source product. That means that a dedicated group of librarians and developers around the world works collaboratively and transparently to patch bugs, create new features and enhancements, and manage the development process; all to make Koha available for free to anyone.
The Koha community produces two major releases per year, in May and November. Every month between the May and November releases, the Koha community produces a smaller release called a “point release” (at ByWater we sometimes call these PS updates – PS is for ‘post script’), containing bugfixes and security updates. Generally, enhancements and new features are reserved for the major releases.
When our partners are upgraded to the newest major release of Koha, their workflows may uncover a bug, or a missed case in the new features. And that’s good! Identifying problems is the first step to fixing them.
After a bug is identified and filed, the Koha community gets to work on patching it. A developer submits a patch to be tested by someone else in the community. After the patch passes testing and Quality Assurance, the Release Manager pushes the new code to the main version of Koha, ie, the next major release. At that point, the patch can be considered for backport to previous versions (in other words, to the version you’re using).
You can read more about the development process on the Koha Wiki.
That’s great, but I can’t make heads or tails of this link that you sent me, and I still don’t know when my problem will be fixed.
There are a lot of words and confusing codespeak on Bugzilla, but when it comes to bug fixes, there’s really just one place you need to look: Version(s) released in.
If there is no version number next to Version(s) released in, that means the community is still working on patching and testing the code that will fix the bug.
In the example below, the bug has been patched, tested, passed QA, pushed to 24.11, and backported to 24.05.06.
So, what version of Koha do you use? The version number is conveniently located on the Koha home screen in the bottom right corner.
Blast! You’re using version 24.05.05, so this bug still exists for you. When will this problem be fixed in your Koha? It’s time to check the calendar!
Our partner libraries receive their point update during the third full week of each month. You will not receive a News item on your staff client like you do for major releases; these updates take place quietly in the background, and the version number will change automatically when your Koha is updated.
If you want to know the specific date of your next point update, please send us a ticket.
Related Articles
Twilio Integration with Koha
Some of our partners subscribe to Twilio for SMS messages and phone notifications from Koha. If you are a ByWater Solutions partner and have a Twilio account, we can help you set up the connection. Twilio SMS Twilio sends the SMS notices that Koha ...Labels in Koha
There are a number of options for creating labels in Koha. Label Creator Koha's label creator tool will allow libraries to use layouts and templates that will assist in the creation to print spine labels and barcodes. A library can create customized ...Koha Glossary of Terms
Find the basics of Koha's vocabulary here This glossary is in alphabetical order. Use control+F to quickly search this page for specific terms. Authority Record: allows your library to control and search fields in your MARC records such as subject ...Koha to Koha ILL
This articles walks through the steps of setting up a Koha to Koha interlibrary loan instance. The ILL (Interlibrary loans) module adds the ability to request and manage loans or copies of material. Patrons can submit a request via the OPAC from the ...Koha Marketing Resources
Is your library getting ready to go live with Koha's OPAC? Here you will find templates and logos to get the process started. Logos Download Koha logos to customize your branding and messages for your community of library users! Koha Logo Files - ...