25 lines
2.1 KiB
Markdown
25 lines
2.1 KiB
Markdown
# Joint release checklist (SLS, ASF, CMS)
|
|
|
|
Replaces the separate Deployment Setup, Monitoring Setup and Production Readiness stages of the features that are merged to master on 2026-11-16 (decision of the owner). Executed once, at the joint release moment. Every step needs the explicit go of the owner.
|
|
|
|
Status on 2026-11-16: everything is merged to master and runs on TEST only. No production release has been made.
|
|
|
|
## Before the release moment
|
|
- [ ] ASF IIS publish pipeline exists (own feature: self-contained win-x64 publish, FTP upload, web.config, the CMS host as the single entry for the website; open hosting questions are answered by trying it with ASF).
|
|
- [ ] Hero module feature decided (release with or without it). SLS side: `docs/hero-integration.md`; production needs the seeded hero in the production CMS, the CMS host with the hero module, and the LCP check on the site afterwards.
|
|
- [ ] Privacy statement and static texts reviewed by the owner (kept aside until now).
|
|
- [ ] Captcha provider decided (Gitea issue #14, `docs/captcha-providers.md` in the CMS repo). Captcha stays OFF in production until then.
|
|
|
|
## Merge state (done 2026-11-16)
|
|
- Order: CMS (`contact-forms-module`) first, then ASF (`asf-packages-cms`, test-only commit d449e76 removed), then SLS (`redesign-modern-timetravel`).
|
|
- A push to master deploys to test only. Production is only started by a manual dispatch (ASF: only from a `release/` branch).
|
|
- CMS branch protection: required checks `backend-test` and `frontend-test` only.
|
|
|
|
## Release steps (production)
|
|
1. SLP production environment: `Website__NoIndex=false`, `Website__PublicBaseUrl=https://slpsoftware.nl`.
|
|
2. Contact retention configured (12 months for messages) and checked.
|
|
3. Deploy CMS (`deploy_sls_production`), then the SLS website (`deploy_production`), then ASF via the IIS pipeline.
|
|
4. IIS passes ALL requests to the CMS host for ASF.
|
|
5. After release: check Sentry (errors, release tag), smoke tests per site, share image and sitemap, contact form end to end (one real message), cookies and statistics as described in the privacy statement.
|
|
6. Update requirements and docs to the production state.
|