The .gov program has decided that the initial launch for public view would allow an org administrator to view and manage their domains for the organization. This will be the first releasable iteration of the org model feature.
This issue will serve as a checklist for launch, presuming all tickets in the m1 and m2 milestones are complete, and is part of the m2 milestone.
Launch checklist
14+ days out
[ ] identify first production user, communicate expectations. (Program/product)
[ ] Re-load sanitized production data on Staging, so it closely reflects reality. (dev)
[x] #2615
[ ] deploy on Staging
[ ] UAT on Staging (Product)
7 days out
[ ] Internal "User" Testing session
[ ] all m1/m2 code deployed to Production (feature flag off)
Day of Launch (cutover)
[ ] enable m1/m2 feature flag (release)
[ ] Confirm proper operations (UAT on Prod)
[ ] customer engaged and using feature.
Additional context
Are there any database migration/preload/configuration changes that need to be "coordinated?"
Issue description
The .gov program has decided that the initial launch for public view would allow an org administrator to view and manage their domains for the organization. This will be the first releasable iteration of the org model feature.
This issue will serve as a checklist for launch, presuming all tickets in the
m1
andm2
milestones are complete, and is part of them2
milestone.Launch checklist
14+ days out
7 days out
Day of Launch (cutover)
Additional context
Links to other issues
Related to:
2674
No response