[koha-commits] main Koha release repository branch master updated. v16.05.00-573-g30a0df4

Git repo owner gitmaster at git.koha-community.org
Fri Sep 2 16:50:57 CEST 2016


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "main Koha release repository".

The branch, master has been updated
       via  30a0df493dc35e3aa9186f3b3c4c212d3b396a65 (commit)
       via  596ddef3c33f675f9daad675512fb119f80a23fa (commit)
      from  bff08b9962318f6eca873693936e369456f428e5 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 30a0df493dc35e3aa9186f3b3c4c212d3b396a65
Author: Kyle M Hall <kyle at bywatersolutions.com>
Date:   Fri Jun 24 15:18:04 2016 +0000

    Bug 11144 [QA Followup] - Let each script run in sequence even if one fails
    
    Signed-off-by: Marcel de Rooy <m.de.rooy at rijksmuseum.nl>
    
    Tested the A;B;C variant here. If A fails, B will run. Since we can safely
    assume that A (or B) will not fail on a daily basis, this seems to be better
    than running them in the wrong order every day.
    
    As the comments on Bugzilla show, several people support this improved
    (reordered) scheme and look forward to improved error handling on another
    report (obviously not that simple).
    
    Signed-off-by: Kyle M Hall <kyle at bywatersolutions.com>

commit 596ddef3c33f675f9daad675512fb119f80a23fa
Author: Katrin Fischer <Katrin.Fischer.83 at web.de>
Date:   Tue Jun 9 23:13:15 2015 +0200

    Bug 11144: Fix sequence of cronjobs: automatic renewal - fines - overdue notices
    
    The patch changes the sequence of cronjobs in the crontab example
    file and in the cron.daily file of the packages.
    
    This is why:
    1) Renew automatically
       ... only when we can't renew, we want to
    2) Calculate fines
       ... once the fine are calculated and charged
       we can print the amount into the
    3) Overdue notices
    
    Before the change it could happen that you'd charge for an item,
    that would then be renewed. Or that you'd try to print fine
    amounts into the overdue notices, when they would only be
    charged moments later.
    
    To test:
    - configure your system so you have items that should
      - be charged with fines
      - renew automatically
    - configure your crontabs according to the example file
      or switch the cron.daily in your package installation with
      the new one
    - configure your overdue notices so that one should be generated
      <<items.fine>>
    - Wait for the cronjobs or schedule them to run earlier
    - Verify all is well and as it should be
    
    Signed-off-by: Chris Cormack <chrisc at catalyst.net.nz>
    
    Signed-off-by: Kyle M Hall <kyle at bywatersolutions.com>
    
    Signed-off-by: Marcel de Rooy <m.de.rooy at rijksmuseum.nl>
    
    Signed-off-by: Kyle M Hall <kyle at bywatersolutions.com>

-----------------------------------------------------------------------

Summary of changes:
 debian/koha-common.cron.daily |    4 ++--
 misc/cronjobs/crontab.example |   10 +++-------
 2 files changed, 5 insertions(+), 9 deletions(-)


hooks/post-receive
-- 
main Koha release repository


More information about the koha-commits mailing list