Preparing for Koha 3.2

In the cycle of Koha development there are slow times and there are busy times. Right now is a busy time. We’re in the run-up to a big release, Koha 3.2. It has been sixteen months since the release of Koha 3.0. Since that time developers have been working on two tracks: The first track is one devoted to bug-fixes and minor enhancements to 3.0.x. The fruits of those labors can be found in the releases of Koha 3.0.1, 3.0.2, 3.0.3, 3.0.4, and most recently 3.0.5. Each of these releases reflects incremental improvements.

At the same time work on major new features has taken place along the other track, the track leading to Koha 3.2. Major new features will often include structural changes like new software dependencies or database structure changes.  For an interface designer like me this track is always the most interesting, because new features means new interfaces to help refine.

This is an exciting time because the Koha project has recently gotten a large contribution of code from BibLibre, a French Koha development and support company. BibLibre has a long history with Koha and a long history with the Athens County Public Libraries: When we were preparing to switch to Koha in 2002 BibLibre answered our RFP to add MARC support to Koha.  Eight years later BibLibre is still a major contributor to Koha. Included in their recent submission is the new acquisitions functionality which Paul Poulain discussed at KohaCon 2009.

Much of what I do when I work on Koha is to look at existing or new interfaces and try to do what I can to make them cleaner, improve their structure, and help the design however I can. Some of these changes are guided by standards, whether they be web standards or simply conventions we’ve adopted for markup and interaction design. When a big contribution like BibLibre’s comes along, I start the process of reviewing every template and every new interface to see if everything works well and looks good. This isn’t just a process about making things look pretty, it’s a perfect opportunity to do some informal usability testing, some bug-hunting, and some bug-fixing.

This is what working on an open-source project is all about: contributing our work to the project to make the best software we can. And the best thing about it is it’s a lot of fun.

7 thoughts on “Preparing for Koha 3.2

  1. Matt B

    Is there anywhere we can download the development releases of 3.2? We want to switch to Koha, but we really need the Patron Label Creator, which is not in 3.0.

    Trying to navigate these version numbers is crazy.

    Reply
  2. Rohan R

    Thinking about Koha for a club library with 15,000 books. Which version should I be targeting to use? 3.0.2? 3.0.5? or should I wait for 3.2 ? I cannot find scheduled release date for Koha 3.2 anywhere. Is Windows support going to be re-introduced in some future version?

    Reply
  3. oleonard Post author

    Rohan, I think the answer depends on a few factors: How soon do you want to go live with your system? How comfortable are you using an unstable version of Koha? Is it necessary to run Koha on Windows? Work is underway to make Koha 3.2 work on Windows again, but it is not done.

    If you can’t wait for 3.2, use the latest stable 3.0.x version, which currently is 3.0.5. See http://download.koha.org.

    (Ignore the fact that the Koha.org home page says 3.0.4 is the latest version. Also ignore the fact that the download page on Koha.org says 3.0.2 is the latest version. Both are wrong, and the current custodian of Koha.org refuses to fix the errors).

    Reply
  4. Rohan R

    Would like to go live in the next three months, would prefer to use a stable version, and not necessary to run Koha on Windows. Would a stable release of 3.2 be available within the next three months?

    Thanks for replying.

    Rohan

    Reply
  5. oleonard Post author

    We’re expecting an Alpha release any day now, but there’s no way for me to predict how soon the official release will come. Personally I’d feel comfortable running the Beta, but you’d need to be prepared to do an update if a critical bug was found (as always I suppose).

    Reply

Leave a Reply to Rohan R Cancel reply

Your email address will not be published. Required fields are marked *