[FOLIO-2475] Release mod-circulation for Q1 2020 Created: 26/Feb/20  Updated: 03/Jun/20  Resolved: 21/May/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P2
Reporter: Cate Boerema (Inactive) Assignee: Marc Johnson
Resolution: Done Votes: 0
Labels: release
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by CIRC-682 Grace period is handled incorrectly w... Closed
is blocked by CIRC-702 Overdue fines not calculating for any... Closed
is blocked by CIRC-524 (1-OD-B-2) Calculate overdue fine usi... Closed
is blocked by CIRC-658 Circulation rules editor allows non-e... Closed
is blocked by CIRC-666 Do not attempt to annonymize loans mo... Closed
is blocked by CIRC-677 (1-OD-D) Overdue fine for item renewe... Closed
is blocked by CIRC-698 Set location name to overdue fine's "... Closed
is blocked by CIRC-699 Bugfest: 500 Error when filtering Req... Closed
is blocked by CIRC-700 Can't check out items with check out ... Closed
is blocked by CIRC-705 Circulation rules editor throwing ina... Closed
is blocked by CIRC-656 Do not create Overdue fine type when ... Closed
is blocked by CIRC-678 Wrong overdue fine value is used when... Closed
is blocked by CIRC-680 Create fee/fine action when overdue f... Closed
Cloners
is cloned by FOLIO-2476 Release mod-circulation-storage for Q... Closed
Sprint: Core: F - Sprint 84
Story Points: 5
Development Team: Prokopovych

 Comments   
Comment by Marc Johnson [ 06/Mar/20 ]

Cate Boerema Darcy Branchini Emma Boettcher Holly Mistlebauer Cate Boerema

According to this, there is only one issue that is needed to be resolved (though that might be complicated) before the release is done.

Is that a reasonable reflection of the situation, there are numerous issues with outstanding pull requests waiting at the moment:

CIRC-677 Closed Do not charge overdue fine when forgiven
CIRC-678 Closed Change how overdue fines are charged during renewal
CIRC-656 Closed Do not create fee / fine type automatically from circulation
CIRC-658 Closed Circulation rule validation

Should I perform the releases irrespective of those?

Comment by Darcy Branchini [ 06/Mar/20 ]

Marc Johnson, thank you, I'm adding these as issues that need to be resolved before the Q1 release.

cc: Alexander Kurash

Comment by Marc Johnson [ 12/Mar/20 ]

Cate Boerema Darcy Branchini Roman Barannyk

How critical is it that CIRC-658 Closed make it into the 2020 Q1 release? It is a substantial change that is still in review. Do we want to expedite it, even if not fully reviewed?

(I've expedited as many of the smaller changes as I can. In general we've pushed cramming in changes quarter further than I am comfortable with).

Comment by Darcy Branchini [ 12/Mar/20 ]

Marc Johnson, in my opinion, with everything that everyone is juggling right now to get Q1 released, it's okay if it doesn't make it. The workaround is that users cannot add enter a non-existent policy into circulation rules. This is a burden on the end user, but we know a fix is coming soon.

cc: Cate Boerema Cheryl Malmborg Holly Mistlebauer Alexander Kurash

Comment by Marc Johnson [ 31/Mar/20 ]

Cate Boerema Darcy Branchini

mod-circulation 18.0.1 has been released, which includes changes for CIRC-699 Closed and CIRC-658 Closed

Comment by Marc Johnson [ 02/Apr/20 ]

Cate Boerema Emma Boettcher

mod-circulation 18.0.2 has been released, which includes changes for CIRC-700 Closed

Comment by Marc Johnson [ 02/Apr/20 ]

Cate Boerema Emma Boettcher Darcy Branchini Holly Mistlebauer

I've updated the dependencies to reflect the must fix issues required for 2020 Q1.

Please can I ask that folks update the links to release issues when deciding that an issue is a must fix for a quarterly release.

Comment by Cate Boerema (Inactive) [ 02/Apr/20 ]

Thanks Marc Johnson. That's a good reminder. When must-fix bugs come in during bugfest, should we link those, as well? I wasn't sure if these release JIRAs were still being used after the initial module release deadline.

Comment by Marc Johnson [ 02/Apr/20 ]

Cate Boerema

I wasn't sure if these release JIRAs were still being used after the initial module release deadline.

Maybe the release JIRA are not intended to be used after the initial release, I don't know (I was trying to adopt the process that had been suggested to me for this quarter).

If they aren't, I should close the ones I've re-opened. Should we have separate JIRA issues for each bug fix release, or not track bug fix releases using JIRA issues?

When must-fix bugs come in during bugfest, should we link those, as well?

Only if we are using these issues for the whole process, rather than only the initial release.

Generated at Thu Feb 08 23:20:55 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.