Skip to content

Operate the four-week server-intake overlap and retire issue intake #1610

Description

@kim-em

This begins only after the production server is announced publicly.

Scope

Monitor severity-high incidents, State/archive/evaluation/release-schedule health, automatic releases, and adoption while issue intake remains open. Give at least two weeks public closure notice, extend the overlap after a serious incident or inadequate adoption, hand off the exact cutoff to the final-inventory issue, and close issue intake only after the final delta and a reviewed retirement packet.

Acceptance criteria

  • explicit UTC overlap start, notice, and cutoff bindings
  • at least four weeks overlap and at least two weeks closure notice
  • no unresolved severity-high incident; adoption and end-to-end operation are adequate
  • issue acceptance stops before the final Results freeze and all pre-cutoff runs drain
  • the retirement packet passes and issue intake closes in a single-purpose change
  • server intake, fallback, and rollback documentation remain verified

Out of scope

External-repository changes, Zulip or third-party PR comments without exact approval, incident-history appendices, premature form removal, or implementing historical replay/migration here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions