Theme release workflow

This is the workflow for releasing the theme to CampusPress and affiliated Pantheon WordPress sites. This workflow was agreed upon by the Web Program Leadership Team in their 2022-10-17 meeting.

1. Theme work happens in Github during the week, focusing on established priorities.
2. On Friday afternoons, we release a new version of the theme on Github.
   1. All releases and release notes are on Github.
   2. We create a pull request to merge the latest theme release to the wordpress-dev.ucsc.edu network.
   3. We create a post on the theme sandbox site on CampusPress DEV that includes:
      1. Release notes
      2. Examples of what changed
      3. The ability to comment on the post (WPLT members)
3. On Monday morning, Rob informs WPLT via Slack (or the post auto-publishes to Slack)
4. WPLT reviews the changes between Monday and Tuesday afternoon.
   1. Feedback in comments on the post, or in WPLT Monday meeting.
   2. Go or no-go decision from the WPLT to release to PROD or hold and revise.
   3. No-go decision pushes release into the following week.
5. Go decision:
   1. Web Team creates a pull request to merge the release to wordpress.ucsc.edu network on Tuesday, between 4pm and 5pm.
   2. CampusPress will merge code between 5pm Pacific on Tuesdays and 6am Wednesday, which is an established ITS maintenance window.

Notes

1. WordPress site owners should be notified of theme updates and changes and given enough time to test their sites (or a reasonable facsimile) on the DEV network.
2. The current workflow focuses on providing WPLT with enough time to test. We should probably move the production deployment day to Thursday so site owners have 3–4 days to test and raise issues.