Versions Compared

Old Version 31

changes.mady.by.user Khalilah Gambrell

Saved on

compared with

New Version Current

changes.mady.by.user Khalilah Gambrell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ActionResponsibleStatus
  •  Update Features' statuses
  •  Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders
  •  Clean up Poppy backlog
Product Owner
  •  Prepare data for Bugfest
  •  Create user stories for Kitfox that outline your needs and instructions
  •  Please consider how to test long lists/tables 
Team

Migration/module upgrade documentation checklist 

Migration Plan

  •  Step by Step instructions for module upgrade
  •  New Infrastructure: N/A 
  •  Config Changes:
  •  Schema Changes: JIRA issues created 
  •  Data Migration:

Migration Testing

  •  What are the configuration Changes?
  •  What are the schema Changes?
  •  How do we test?
Team

Action item: Schedule a meeting with Sobha to discuss call number browse migration sometime in the next sprint. Ask Natalia to organize 

Action item: Schedule a discussion with Sobha related Authority record moves. Taras is working on a db script. Maybe we need a story? 

Action item: Need to schedule a meeting to discuss with Implementation - Data Migration folks the Authority API move. Ask Natalia to organize. 

Authority API move - Any impact to National Library of Australia? And Michigan State? 

Action item: Viacheslav Kolesnyk will update release notes 




Any breaking changes? 

TeamYes, Authority API move is a breaking change. We need detailed release notes

Re-Indexing for release upgrade? For bugfest? Consortia test environment? 

  •  Required
  •  Timing 

  • Production libraries = Yes 
    • Dependency is on PTF stories. Follow up with Martin and DA. 
  • Bugfest = Yes
    • Dependency is on PTF stories. Follow up with Martin and DA. 
  • Consortia integration environment = N/A it is new 

Need to add release notes

  • Add release notes 
    •  Include any previous release notes that still relate to the release 
    •  flag any known items with the label  known-issue-<<release>>
    •  See document - Release Notes Overview
PO and Dev lead

Releases notes - we need to add 

  • Authority API breaking changes documentation
    • enabling with loadReference=true
  • Call number browse data migration documentation 
  • Update consortia mod-search documentation (Slava) 
  • Permissions (Christine/KG) 
  • Authority Auto-linking tenant level  configuration (for non-consortia and consortia) 
  • Reindexing improvements based on UXPROD-3936
  • Add any new permissions (like
    Jira Legacy
    serverFOLIO Issue TrackerSystem JIRA
    serverId6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc
    keyUINOTES-141
    )
  • Need to add a note about one instance of quickMARC needs to be run. IOW quickMARC module is not HA

Accessibility Testing

TeamDone
  •  Conduct or create user stories for performance/load testing. See Types of tests
Team

Document Potential Risks and Risk Mitigation Plan

Risks:

  •  Linking (consortia) feature 
  •  Folijet development... dependencies 
  •  Call number browse by type feature (migration) 
    •  We need to talk with FSE hosting 
Team

Did the 9/14 discussion happen? 

Christine has created a decision log 

Meeting with POs + QA for 9/27 

...

ActionResponsibleStatus
  •  Update Features' statuses
  •  Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders
Product Owner
  •  Prepare data for Bugfest
    •  Create user stories for Kitfox that outline your needs and instructions 
      •  FWIW - I think settings needs to be cleaned
    •  Please consider how to test long lists/tables 
Team
  • Add release notes 
    •  Include any previous release notes that still relate to the release 
    •  flag any known items with the label  known-issue-<<release>>
PO and Dev lead

Accessibility Testing

Team
  •  Conduct or create user stories for performance/load testing. See
Types of tests		Product Owner writes user stories. TBD who will conduct. 

Sprint before Bugfest (aka Business Acceptance Testing) period (176)

ActionResponsibleStatus
  •  Update Features' statuses
  •  Identify which features are at risk and the "at-risk" label to the feature.
Product Owner
  •  User stories: update Release field for those stories/bugs/tasks/etc that will not be done for the release. 
Product Owner
  •  Generate Release Artifacts (see Orchid) and link to Release notes 
Team 
  •  Add release notes 
    •  Include any previous release notes that still relate to the release 
    •  flag any known items with the label  known-issue-<<release>>
PO and Dev lead
Team

Team meets with Kitfox to review upgrade instructions. 

Team's accept Bugfest build. Need to consider Consortia support. 

  •  Teams must conduct smoke tests to verify key functionality works as expected BEFORE Bugfest is made available to community 
  •  Teams must document 
    •  App/module not ready for testing 
    •  Issues yet to be resolved
  •  Deployment verification? 
Team
Regression testing? QA?
  •  Conduct performance/load testing. See
Types of tests		Product Owner writes user stories. TBD who will conduct. 

...

Sprint before GO-Live (178)

ActionResponsibleStatus
  •  Update Features' statuses
  •  There should be no at-risk feature 
Product Owner
  •  Add/Review release notes 
    •  Include any previous release notes that still relate to the release 
    •  flag any known items with the label  known-issue-<<release>>
PO and Dev lead 
  •  Complete remaining performance/load testing. See
Types of tests		Product Owner writes user stories. TBD who will conduct. 

...

Go-Live sprint

ActionResponsibleStatus
  •  Teams must conduct smoke tests to verify key functionality works as expected
Team

Testing: All Karate tests and e2e tied to release functionality should be done and running 

Team
  •  Add/Review release notes 
    •  Include any previous release notes that still relate to the release 
    •  flag any known items with the label  known-issue-<<release>>
PO and Dev lead

...