Hello!
Yesterday afternoon I download the 3.0.5 version and after 1 hour I see the
3.0.6 version ready to download.
Does anyone know why this big differences on tar size?
koha-3.00.05.tar.gz 94 Mb
koha-3.00.06.tar.gz 20 Mb
harley.tar.gz 21 Mb
Thanks in advance
Evelio
2010/5/19 Evelio Martínez eve...@masmedios.com:
Hello!
Yesterday afternoon I download the 3.0.5 version and after 1 hour I see the
3.0.6 version ready to download.
Does anyone know why this big differences on tar size?
koha-3.00.05.tar.gz 94 Mb
koha-3.00.06.tar.gz 20 Mb
harley.tar.gz
Given that this discussion has been somewhat carried on through the
wiki (http://wiki.koha-community.org/wiki/General_Meeting,_June_2_2010),
I thought it would be good to keep it on list as well.
MJ posts the following argument to the above referenced agenda:
* AGPL does not prevent unfriendly
Hi all,
Just a ´dumb´question from someone who just started submitting a few minor
patches:
Galen wrote:
This patch is similar to commit 731b82f7641565c, which is present in
HEAD and, if this is a significant enough issue in 3.0.x, should be
cherry-picked to that branch. I've marked bug
2010/5/19 Marcel de Rooy m.de.r...@rijksmuseum.nl:
Hi all,
What is the procedure for a patch to reach 3.0.x too (in general; this patch
is not that relevant) ?
Just put a [3.0.x] in the subject line of your patch if it is 3.0.x
specific. Otherwise, make a note what all it applies to in the
Hello,
After looking into the code of the predefined report Patrons with No
Checkouts (borrowers_out.pl), I wonder whether the way it is generated
(at least in Koha version 3.0.5) is a Bug:
It only takes into consideration old_issues table, which means that
Patrons having items for the first time
While we're talking about availability, thought I'd put this out there.
Our statewide ILL system would really appreciate a single field for
availability on items: a yes, you can have that for ILL or No, I'm sorry,
that item is lost, checked out, out for repair, local use only, In transit, or
On ke, 2010-05-19 at 07:23 -0400, Chris Nighswonger wrote:
Given that this discussion has been somewhat carried on through the
wiki (http://wiki.koha-community.org/wiki/General_Meeting,_June_2_2010),
I thought it would be good to keep it on list as well.
For what it's worth, I agree: it's
Liz,
I've been thinking about that for a while now. I'd like to see a partially
user-configurable status setting, that includes some core status (checked
out, in transit, on order, etc.), as well as the ability to define new
ones. Status would be a code, a staff client name, an OPAC name, and
