ERM Sprint 151

ERM Sprint 151

Sprint Goal / Focus

  • Nolana: Module Release Deadline

  • Orchid: Development Starts

Sprint Schedule

  • Sprint: 151

  • Release: 2022.3 Nolana  

    • Sprint 9 of 9 since Release Development Cycle Starts (Sprint 142) to Feature Freeze (Sprint 150)

    • Sprint 151: Module Release Deadline [FOLREL-549]

      • Backend 26 Oct 2022

      • Frontend 28 Oct2022

    • Sprint: Bugfix Release Deadline (2 Dec 2022) [FOLREL-550]

  • Release: 2023.1 Orchid  

    • Sprint 1 of 8 since Release Development Cycle Starts (Sprint 151) to Feature Freeze (Sprint 158)

    • Sprint 159: Module Release Deadline [FOLREL-???]

      • Backend 22 Feb 2023

      • Frontend 24 Feb 2023

    • Sprint: Bugfix Release Deadline (2 Dec 2022) [FOLREL-???]

Development Meetings

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Monireh: AL 24-28 Oct

Lead Roles:

  • Code Review: @Ethan Freestone

  • QA:  @Owen Stephens 

QA Environment: 

Present

  • @Jag Goraya 

  • @Ethan Freestone 

  • @Monireh Rasouli 

  • @Claudia Malzer 

  • @Peter Böhm 

Planning Questions

  • Does the issue meet the criteria for Definition of Ready?

  • What front and back end components are affected?

  • What changes need to be made? (additions, removals or modifications)

  • What development tests need to be written?  

  • What data does the developer need to verify their work?

  • What are the known unknowns? 

  • What is needed to QA? (environment, data, scripts)

Navigation

  1. Sprint Goal / Focus

  2. Sprint Capacity

  3. Review sprint candidates 

  4. Agree technical approach / define key implementation tasks

  5. Finalise estimates / costings

  6. Confirm sprint scope

  7. Confirm first actions

 

 

 


Sprint Planning  

 - not in sprint

 or @ - in sprint 

- not ready

- pending triage / planning

 

Planning Notes Template

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Development Estimate

Sprint Focus

Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

 

 

 

No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

https://folio-org.atlassian.net/browse/ERM-2382

 

  • Triage

    • no obvious reason why this should happen

    • could be stripes, could be memo-ising issue

    • kint-components / search and sort

  • Approach

    • q-index is grabbed from url

    • stripes might be memo-ising > timing / race condition issue

    • set another parameter to intercept

  • Components and Changes

    • Frontend: 

    • Backend: potentially a kint-components issue

  • Tests / Data / Dependencies.

  • Known Unknowns

    • not clear why it's triggering once q-index is not being replaced

  • QA: snapshot | local | testing | other

  • Development Estimate: 

    • timebox 1d

https://folio-org.atlassian.net/browse/ERM-2387

@Peter Böhm 

  • Triage

  • Approach

    • Add package name to list of properties handled 

  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements 

  • Tests / Data / Dependencies: NA

  • Known Unknowns: NA

  • QA:

    • package name: local via JSON 

  • Development Estimate:  0.25d

https://folio-org.atlassian.net/browse/ERM-2384

@Ethan Freestone 

  • Triage

  • Approach

    • Cherry pick  changes needed

    • Add implementer notes for how to see benefit

    • No special release to be published, just update codebase for implementers to rebuild from

  • Components and Changes

    • Frontend: stripes-kint-components

    • Backend

  • Tests / Data: rebuild environment as part of dev process

  • QA: to be done as part of dev testing

  • Development Estimate: <0.25d

https://folio-org.atlassian.net/browse/ERM-2388

 

  • Approach

    • Package ID (eg, ISIL) might need to be deprecated rather than removed

    • iterate over the list to avoid database churn

  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements / packageIngestService (line 116 onwards)

  • Tests / Data / Dependencies: NA

  • Known Unknowns: NA

  • QA:

    • package ID: snapshot

  • Development Estimate:  0.5d

Release Tasks (Nolana)

Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

https://folio-org.atlassian.net/browse/ERM-2331

@Ethan Freestone

 

https://folio-org.atlassian.net/browse/ERM-2384

 

 

 

 

 

Changes

Added

Removed: note whether rescheduled or deferred

 

 

 

Planning Notes Template

  • Current State

  • TODO

  • Development Estimate

Rolled Over From Previous Sprint

In Development

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

 

https://folio-org.atlassian.net/browse/ERM-2261

@Peter Böhm 

  • Current State