Hi All Ian (the QA manager) and I thought for 3.6.x it might be an idea to send an email each week, highlighting some bugs we would love people to look at. This is not to say, you shouldn't try to sign off all of them :-) But I will attempt to highlight ones that are critical, major, or just cool. Bug 4993 ldap search always uses anonymous when binding by auth Bug 5683 link_bibs_to_authorites.pl can corrupt records Bug 5995 Glitch with checkauth Bug 5724 Sometimes deletes aren't processed correctly by rebuild zebra Bug 5093 JS in IE8 when choosing authority record Bug 6034 Sheliving cart feature can wipe shelving location Bug 5872 Enhancemens to circulation management Bug 5905 Partial fine payments Bug 5184 Upgrade Jquery 1.4.2 Bug 5605 Add Support for SIP Fee Paid Message Bug 5572 refinements to function merge sub merge in C4::AuthoritiesMarc Bug 5009 add autocomplete="off" to borrowernumbers and barcode forms This is just a selection I pulled out, if you have time take a look, the earlier they get checked, the easier they are to merge :) Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
Le 01/05/2011 23:07, Chris Cormack a écrit :
Hi All Hi Chris, Ian (the QA manager) and I thought for 3.6.x it might be an idea to send an email each week, highlighting some bugs we would love people to look at. This is not to say, you shouldn't try to sign off all of them :-) But I will attempt to highlight ones that are critical, major, or just cool. That's what I intended to do with my weekly hacker's corner -which, obviously is not really weekly :( - Does it mean you think I should stop trying to send a "weekly" hacker's corner mail ?
<snip> I want to encourage specifically ppl to work on those two :
Bug 5872 Enhancemens to circulation management This one may seem very basic in its description :
"everything (issues, holds, fines) now at granular level" but it's a huge stuff from BibLibre, and it's a great feature ! It means you can have all issuingrules related things at branch/itemtype/categorycode level Ie : you can define how many issues (like previously) and holds and fines you have. There is some inheritance, that look like what we had in 2.2, except that it is highly visible for the librarian. If you want to know what it looks like head here: http://borrowers34.git.biblibre.com/cgi-bin/koha/admin/smart-rules.pl (login test/test) you'll see that the default rule is 12 checkouts for 10 days, with 1 renewal for 5 days,... The 2nd line says that for "Computer files" the 12 checkouts (inherited from the default, it's in grey) are for 21 days (in black: not inherited) more = do a double click on a given value and you can modify it (save with <enter>) directly You'll also notice the "suspension duration" column : in France, 99% of the libraries have fines in days. You check-in 4 days late ? You can't checkout for 4 days ! I think it's too bad this patch hadn't been applied for 3.4, but if you want it for 3.6, you should sign-off it ! ( you can also note that, as it's a huge stuff, the sooner it's included, the better it is = hdl spent 3 days during hackfest to have the branch working with HardCodedDuedates. And it's something we did almost 2 years ago ! )
Bug 5905 Partial fine payments This one is very interesting too (and from BibLibre too).
The description is in the rebased patch from Julian: Bug 5905: lot of updates for borrower's fines adding a primary key id on accountlines table and updating calls on specific entries on this table adding a meansofpayment field on accountlines table and a MeansOfPayment syspref to define a list of means of payment. adding management of means of payment for borrower's fines adding management of part payments for borrower's fines adding jquery.tablesorter and jquery.tablesorter.pager support for boraccount.pl and jquery.numeric support for the others borrower's fines pages replacing in pay.pl the majority "$input->param( $names[ $i + a variable number ] )" occurrences with "$input->param( the beginning of inputname + id on accountlines ] )" for a better understanding of the code adding javascript functions to disable negative numbers content on text's numeric's inputs, redefine values of Part payment's inputs where it's higher than the Amount Outstanding, manage readonly params for Part payment's inputs adding time on boraccount's page HTH -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
On 3 May 2011 01:59, Paul Poulain <paul.poulain@biblibre.com> wrote:
Le 01/05/2011 23:07, Chris Cormack a écrit :
Hi All Hi Chris, Ian (the QA manager) and I thought for 3.6.x it might be an idea to send an email each week, highlighting some bugs we would love people to look at. This is not to say, you shouldn't try to sign off all of them :-) But I will attempt to highlight ones that are critical, major, or just cool. That's what I intended to do with my weekly hacker's corner -which, obviously is not really weekly :( - Does it mean you think I should stop trying to send a "weekly" hacker's corner mail ?
I don't think so, the more the merrier Chris
participants (3)
-
Chris Cormack -
Chris Cormack -
Paul Poulain