Release Manager for 3.4 elected

And in the final (maybe) piece of Koha news today. I have just been voted in as the Release Manager for the 3.4 release of Koha. The next general meeting will include the voting for the other positions, such as Translation Manager, QA Manager, Bug wrangler etc.

I will be staying on as Translation Manager until a new one is elected and we hand over, and for the remainder of the 3.2 release (alpha due any day now) Galen is the release manager still.

I’m honoured that the community has placed this much faith in me, and I know I have a huge act to follow after Galen. It has been almost 8 years since I was last Koha release manager … there have been 83 new people who have committed to the Koha code base in that time, and a much larger pool of active developers.  I will do my best to remain open in communication and to listen to all opinions. My proposal for 3.4 can be read here, it is of course not set in stone.

4 thoughts on “Release Manager for 3.4 elected”

  1. Congratulations! I’m convinced you’ll be the right person in the right place, especially in the upcoming new Koha environment.

    We had a talk a while back about 3.4 aims and technologies to use. I’ve played with integrating Moose into Koha. It may be a goal for Koha 3.4 and would allow to clean up the code. As a proof of concept, I’ve developed few scripts available here:

    http://git.tamil.fr/?p=tkoha

    or clonable:

    git clone git://git.tamil.fr/git/tkoha

    Perl Moose module must be installed, of course.

    Two scripts work as a rebuild_zebra.pl replacement :

    – bin/koha-index
    – bin/koha-index-daemon

    Both are autodocumented with Perldoc.

    1. They look really promising Frederic. And I think this is definitely a way forward we want to explore. The nice thing about doing it this way, is that we can incrementally switch. We don’t need to break everything all at once.

      I’ll certainly want to chat about this more on irc :)

Comments are closed.