evergreen:tags/rel_2_11_6

Last commit made on 2017-06-21
Get this branch:
git clone -b tags/rel_2_11_6 https://git.launchpad.net/evergreen

Branch merges

Branch information

Name:
tags/rel_2_11_6
Repository:
lp:evergreen

Recent commits

4f045be... by Dan Wells

Bumping version numbers, adding Upgrade Script and Changelog

Signed-off-by: Dan Wells <email address hidden>

8bef3a1... by Dan Wells

Bump OpenILS.pm version

Signed-off-by: Dan Wells <email address hidden>

5a565d9... by Kathy Lussier

Docs: Release Notes Fix

No, release 2.11.6 is not a security release.

Signed-off-by: Kathy Lussier <email address hidden>

65957ff... by Kathy Lussier

Docs: 2.11.6 Release Notes

Signed-off-by: Kathy Lussier <email address hidden>

c801e88... by Chris Sharp

LP#1694696 - Check for blank SMS Carriers in A/T reactor

Currently, the get_sms_gateway_email subroutine does not check
for the truthiness of sms_carrier, which can result in catastrophic
failure for a running server. This adds that check.

Signed-off-by: Chris Sharp <email address hidden>
Signed-off-by: Galen Charlton <email address hidden>

96ea98c... by Galen Charlton

LP#1694696: add some unit tests for A/T helpers

In particular, start with get_sms_gateway_email().

Signed-off-by: Galen Charlton <email address hidden>

7dddee8... by Dan Wells

LP#1686194 Account for adjustments when generating fines

Fine generation stops at a predetermined 'max fines' amount, but this
does not account for possible adjustments which lower the effective
fine amount. This situation is common in cases where lost items are
returned, and the library wants to generate additional overdues upon
that event.

With this commit, fine generation will pull in any adjustments applied
to overdue fines, and use those to offset the current total fine when
checking for max fines.

Also includes test for this condition.

Signed-off-by: Dan Wells <email address hidden>
Signed-off-by: Jeff Davis <email address hidden>
Signed-off-by: Galen Charlton <email address hidden>

3c81ca6... by Jason Boyer

LP1690434: Date Comparisons in the Reporter

Because of the way the where clause is constructed
in queries using the Year + Month Transform reports
using some types of operators could produce invalid
SQL.

To test:
put together a simple report template with a date
in the Basic Filters section, using the Year + Month
transform and the On or After operator. (a count of
circs with an xact_start filter is a simple way to
set this up.) Schedule it with a relative date
such as 1 month ago and run it.

Pre Patch: the report will fail and the error text
will reference a missing text >= double precision
comparison function.

Post Patch: you'll get a count of how many circs
were opened last month (or whatever report you
wrote).

Signed-off-by: Jason Boyer <email address hidden>
Signed-off-by: Mike Rylander <email address hidden>

b3bb7c1... by Galen Charlton

LP#1312824: follow-up to fix whitespace

Signed-off-by: Galen Charlton <email address hidden>

eeaa825... by Kathy Lussier

LP#1312824: Change success message for transferred holds

The holds transferred success message should clarify which holds were
transferred to mitigate potential confusion.

Signed-off-by: Kathy Lussier <email address hidden>
Signed-off-by: Galen Charlton <email address hidden>