Versions Compared

Version Old Version 6 New Version Current
Changes made by

Charlotte Whitt

Charlotte Whitt

Saved on

Key

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

Two sprints before feature freeze (209) 

...

Action

Responsible

Status

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

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?
Index Data





Any breaking changes? 

ThorNo

Re-Indexing for release upgrade? For bugfest Sunflower?

-No
  • 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
Charlotte, as product owner 

Has begun adding notes.


Accessibility Testing

--
  •  Conduct or create user stories for performance/load testing. See Types of tests
N/A-

Document Potential Risks and Risk Mitigation Plan

Risks:

N/A

-

...

Action

Responsible

Status

  •  Update Features' statuses
  •  Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders
Charlotte as Product OwnerDone
  •  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 
Charlotte working with with KitFox team on bound+with data (BF-773)
  • Add release notes 
    •  Include any previous release notes that still relate to the release 
    •  flag any known items with the label  known-issue-<<release>>
Charlotte, as Product Owner together with TeamIn progress

Accessibility Testing

--
  •  Conduct or create user stories for performance/load testing. See
Types of tests		N/A-

Sprint before Bugfest (aka Business Acceptance Testing) period (

...

213)

Action

Responsible

Status

  •  Update Features' statuses
  •  Identify which features are at risk and the "at-risk" label to the feature.
Charlotte, Product Owner
  •  User stories: update Release field for those stories/bugs/tasks/etc that will not be done for the release. 
Charlotte, Product Owner
  •  Generate Release Artifacts (see Orchid) and link to Release notes 
Thor 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>>
Charlotte, Product owner
Thor team

Team meets with Kitfox to review upgrade instructions. 

Team's accept Bugfest build. 

  •  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? 
N/A-
Regression testing? 

  •  Conduct performance/load testing. See
Types of tests		Charlotte, Product Owner writes user stories. TBD who will conduct. 

...