Release 3.1Stabilisation
Stabilisation & Hardening
Post-go-live production fixes and hardening measures
Following the go-live of v3.1-Ordering on 4 February, the team entered an intensive stabilisation phase. 12 distinct production issues were identified, triaged, and resolved - most within 1–3 hours of being reported.
Issues by Severity
| Priority | Issues | Examples |
|---|---|---|
| Critical | 4 | SLA defaulting, portal access bypass, notification failures, order notes data loss |
| High | 5 | Dashboard 403s, file upload failures, permit category misalignment, resubmit button exposure, manage delays logic |
| Medium | 3 | Map display, rejection reasons, BP status dating |
Resolution Pattern
The typical cycle was:
- Matt reports issue from customer/user feedback
- Mark or Jayrex investigate and reproduce
- Fix developed and deployed (often same-day hot-patch)
- Matt validates with end users
Most issues were resolved with production hot-patches rather than waiting for scheduled releases.