Skip to content

SCuBA Goggles v1.0 Release Checklist #879

@jkaufman-mitre

Description

@jkaufman-mitre

Prerequisites

  • This issue has an informative and human-readable title.

💡 Summary

This epic focuses on creating a comprehensive release checklist for v1.0. The checklist will serve as a guide for the Goggles team to ensure that all necessary steps are completed before the release.

Pens Down on Baseline Changes: May 1, 2026
Tentative Release Date: July 13, 2026 (Subject to Change)

DEVELOPMENT TEAM:

PMSS TEAM:

  • Coordinate with Directives team on changes to BOD pages
  • Pre-stage BOD IG page with any edits or changes the need to be updated from the latest release
  • Pre-stage BOD splash page
  • Pre-stage SCB policies on the GWS pages
  • Coordinate SCuBA releasing to GovDelivery
  • Post to Slack channel and community connect
  • Publish GovDelivery email
  • Publish GitHub repository updates
  • Send Web Publishing links to updated baseline Drupal pages for publishing
  • Send Web Publishing links to updated BOD Drupal pages for publishing
  • Publish social media
  • Share consolidated change document in Teams chat (GWS)
  • Google Blog Post
  • PMSS CISA announcement
  • Coordinate with Directives for awareness and questions
  • Inform leadership with the expected SCB update release date
  • Develop release shared folder and draft accompanying material (Slack channel, community connect, GovDelivery email, social media, blog post, etc. ) for SCB Update Release (Link folder)
  • Submit consolidated change document and associated release materials (i.e. GovDelivery, social media, blog posts, etc.) for comms approval
  • Set final deployment date for SCB public release
  • v1.0 Baseline Consolidated Change Document
  • Implementation Guide (if just the readme then this is done by SCuBA team, clarification needed)
  • On-boarding Document
  • BOD Pages Update via Directives
  • Update Drupal site (with policies that were updated to the BOD)
  • SCB comms approval (List release name and version number)
  • Review release shared folder content

Motivation and context

N/A

Implementation notes

N/A

Acceptance criteria

  1. A draft of the release checklist is created and reviewed by the team.

Sub-issues

Metadata

Metadata

Labels

Release ChecklistThis issue is part of the Release Checklist.epicA high-level objective issue encompassing multiple issues instead of a specific unit of work

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions