-
Notifications
You must be signed in to change notification settings - Fork 0
Launch Checklist
- Reviewed approval and a separate retryable setup step.
- Credential repair that preserves agency information and reports old-password cleanup failures.
- Source-based post/page creation, editing, UTC scheduling, trash, stale-edit checks, and uncertain-create protection.
- Bounded collection pagination and native table/form/save-status components.
- Redacted local support diagnostics.
- Automated credential lifecycle, real content round trips, two-window isolation, accessibility checks, deterministic packaging, and 10/20/30-site load fixtures.
- 0.10 work: publishing options, encrypted draft recovery, media upload, comment replies and reviewed moderation, synchronization diagnostics, explicit team grants, and 30/50/100-origin testing.
- End-user README; setup, coverage limits, security, and operational detail in this wiki.
Engineering update: the four bug-hunt findings and the six 0.10 feature areas are implemented. The final release commit passed hosted build, quality, Plugin Check, real upgrade/clone, three-browser mutation/isolation, and saved multi-window gates. The saved-window fix still has not shipped in an OpenStation release, and the interrupted 48-hour attempt has not been restarted or completed. These items remain important operational-hardening work after release.
- Dependency and distribution: get the saved-instance fix reviewed, merged, and into a public OpenStation package; replace Fleet CI's temporary PR-commit pin with that released commit. Choose GitHub-only or WordPress.org and test the exact downloadable Fleet/OpenStation pair. Do not instruct ordinary users to rely on an unspecified trunk or PR build.
- Pilot: recruit at least three agencies on different hosts. Give them staging sites and ask them to connect without live assistance, manage two sites at once, repair a revoked connection, and disconnect. Record completion time, blockers, support contacts, and incorrect-site actions. Require zero credential leaks, unintended writes, or lost saved data.
- Hosting matrix: test HTTPS redirects, subdirectory installs, plain/pretty permalinks, security plugins, Authorization-header forwarding, read-only filesystems/FTP prompts, disabled cron, and supported PHP/WordPress versions across independent providers. The local MySQL/MariaDB lab does not replace this.
- Recovery and endurance: back up the hub database/files and salts securely; prove restoration on an isolated clone. Complete a fresh uninterrupted 48–72-hour soak on the final dependency/package pair. Revoke pilot credentials when tests end. Validate interrupted setup and uncertain creation; do not promise automatic rollback.
- Support/security: name the response owner, publish a private security-reporting channel, document response expectations, and review redacted reports before sharing. GitHub public issues are for non-sensitive bugs.
- Release gate: run all checks on the final ZIP, verify artifact checksum, deploy to clean staging, and retake screenshots if visible UI changed. Freeze the supported feature list and changelog. Obtain explicit approval before publishing.
A candidate passes only when all core workflows work on the chosen hosting matrix, agencies can onboard using the documentation, saves hit the correct remote site, and revocation/recovery work as documented. Record unresolved issues with severity and reproduction. A local green test suite is not a public-launch certification.
Keep the prior ZIP and a pre-upgrade hub backup. Disconnecting is a deliberate credential operation, not an uninstall side effect. If an update fails, stop new onboarding/writes, capture a redacted report, restore a known-compatible package pair on staging, and verify stored connection generations before reopening access. Restore database/salts only from a matched backup; copying stale records over repaired connections can resurrect obsolete state.
The current GitHub release is tracked in the 0.10.0 release record. Dependency, endurance, pilot, hosting, and support work above remains open and should be completed before broad production rollout.