Now that the release is out, I wanted to give a quick little update for the following release. I will be traveling out of the country from December 1st till December 10th. Really what my plan is that the first few weeks we will not really be pushing new features. We want to concentrate on any bugs that are needed for 3.22.x and master. Kyle will be in the office and handling those needs. He will push and work on those bugs for us. Once I am back and settled in I will concentrate on bugs and new features. I am very open for discussion and I would like to talk with as many of you as I can about the great work that you're doing. Perhaps I will get a chance to speak with each of you about your plans development wise the next few months - so we can have a clear path on timing, getting you help testing your developments, and of course working with the whole team to help QA code. I think as long as we keep our expectations on the same page, we'll have a lot of success helping you meet the goals of a great stable release. Anything that we can do to help promote more initial sign-offs (probably our biggest bottleneck) the better. Let's see what things we can implement to encourage more of us testing the code. I will be encouraging our partner libraries and our staff to be doing as much as we can even with our busy schedules. Be proud! I plan on doing a weekly release newsletter. Thanks and as always don't hesitate to ask some questions. Brendan A. Gallagher
Really what my plan is that the first few weeks we will not really be pushing new features. We want to concentrate on any bugs that are needed for 3.22.x and master. Kyle will be in the office and handling those needs. He will push and work on those bugs for us. sounds fair & logic. I am very open for discussion and I would like to talk with as many of you as I can about the great work that you're doing. Perhaps I will get a chance to speak with each of you about your plans development wise the next few months - so we can have a clear path on timing, getting you help testing your developments, and of course working with the whole team to help QA code. I think as long as we keep our expectations on the same page, we'll have a lot of success helping you meet the goals of a great stable release. I have to write something about my plan to link Koha and Coral. For
Le 28/11/2015 21:53, Brendan Gallagher a écrit : public libraries, electronic serials are not a big deal, but for universities, it is THE major deal now. We must address this. Instead of adding the feature to Koha, I prefer linking Koha and Coral, an ERMs that is doing a good job. I'll come back with details ASAP (and patches are probably not for the next 3 months)
I plan on doing a weekly release newsletter. I hope you'll be successful. But I fear "weekly" will be a too big job.-- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries
Salvete! This is what you mean, right Paul? http://coral-erm.org/ As usual, I agree with Paul's line of thought. I have wondered an awful lot over the years what things would be like were Koha to be treated like a racecar with modules. If we strip things down to the chassis and allow Libraries to select modules that are relevant to them, I can only imagine that it would be far more usable and perform much better. Just as I felt that leveraging Solr was in our interests and cleverly engineering things for interoperability was vastly preferable to reinventing the wheel. I realise that currently you can configure preferences to be extremely granular. That's great, but what if folks just want something that makes sense out of the box for their type of Library? Cheers, Brooke
participants (3)
-
Brendan Gallagher -
BWS Johnson -
Paul Poulain