Cypress Release Checklist

Cutting RC On or About: 7/6

Aim to have final release out: 7/24 - 7/30

DoneItem (JIRA ticket, if applicable)TeamDue Date
  •  

Make & Announce Dates for Cutting Cypress


Announce to internal teams and edx-code
Make sure Solutions team on board 

Open Source

Sarina Canelake (Unlicensed)

 

mid-June
  •  

Figure out what services to include in the release

See lower on this page

Product

Beth Porter (Deactivated)

mid June
  •  
Tag a sane ref in the repos

Open Source

David Baumgold (Deactivated)

Week of 7/6
  •  

Build new base boxes

Includes: making and executing a test plan; building boxes for bugfix cycles

DevOps

Edward Zarecor

Week of 7/6
  •  
Coordinate with Documentation release notes

Docs, + Open Source support

hoeberR (Deactivated), David Baumgold (Deactivated)

Alison Hodges

Week of 7/22 (start week of 7/6)
  •  

Bugfix Cycle Coordination

Includes: communication with developers (internal & external) about Cypress awareness,
charting what needs to get into the RC,  working with Ops to get new boxes made

Open Source

David Baumgold (Deactivated)

Cypress BugfixesDavid Baumgold (Deactivated)

7/6 -> release date
  •  
Migration Scripts

DevOps, + Open Source support

Edward Zarecor, David Baumgold (Deactivated)

Week of 7/13 -> release date
  •  
Advertising & Marketing

Open Source

David Baumgold (Deactivated)

7/30 (should start ASAP)
  •  
Make a plan for Bitnami, & communicate it with Bitnami

Product

Beth Porter (Deactivated)

7/31
  •  

Make a plan for security fixes

Document SLA around security fixes for named releases going forward
(working group; figure out what constitutes a need for named release security patch) 

Open Source + Ops

Ned Batchelder, Edward Zarecor, David Baumgold (Deactivated)

7/31

 

What Services to Include in the Release

  • edx-platform
  • configuration
  • cs_comments_service
  • notifier
  • edx-certificates
  • xqueue
  • ORA2
  • XBlock

Removing:

  • All ORA1 supervisor services

 

Not Including:

  • Student notes (want to for Dogwood)
  • Badging (want to for Dogwood)
  • Insights (Need to figure out what it means to include, and how to support)
  • ecom stack (Need to figure out what it means to include, and how to support)

Plan for Dogwood is starting here: Dogwood including child pages on how to support the above four services