Page Comparison

•  Update Features' statuses
•  Identify which features are at risk and the "at-risk" label to the feature.

•  User stories: update Release field for those stories/bugs/tasks/etc that will not be done for the release. 

•  Generate Release Artifacts (see Orchid) and link to 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>>

•  Modules Ready for deployment
  •  

    Deployment information is provided in launchDescriptor section of module descriptor.  

  •  Review test status - Unit, Integration, e2e tests
  •  https://jenkins-aws.indexdata.com/job/Testing/job/Scheduled%20Karate%20Tests/600/cucumber-html-reports/overview-features.html
  •  Tickets will be created automatically for each failure. 

Team meets with Kitfox to review upgrade instructions. 

Team's accept Bugfest ECS and non-ECS builds. 

•  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? 

•  Met with FSE hosting to review release notes/instructions

•  Conduct performance/load testing. See