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. 

• Add release notes 
  • Include any previous release notes that still relate to the release 
  • flag any known items with the label  known-issue-<<release>>

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

• Conduct performance/load testing. See

• Update Features' statuses
• There should be no at-risk features

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

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

• Complete remaining performance/load testing. See