Address issues reported by the community during the alpha test phase, and test internally. When we are confident that outstanding issues have been resolved, replace byzantium in shipping.

This is mainly a time-based milestone with active maintenance, as it is impractical for us to qualify a release across all countries / cellular carriers / usage patterns / apps / etc. with internal effort alone. We must rely on community feedback as a key part of this qualification.

Complete any changes needed to flashing stations or installation procedures to use crimson.

Complete when:

• Incoming issue reports from alpha tests have slowed to an acceptable rate
• We have addressed reported issues that must block a general release (generally, regressions over byzantium, but can be assessed individually)
• Crimson replaces byzantium in shipping, for both Librem 14, Mini v2, and Librem 5

Opportunities for improvement over byzantium do not need to block the release. These can come incrementally following the release if possible in updates. Improvements not possible in updates (e.g. switch to pipewire) should be deferred to dawn.

For PC, we estimate ~2 days/week of 1 person should be able to keep up with most reports and address the most significant issues. About 1 month of feedback is probably needed for sufficient confidence in a release.

For Librem 5, an additional ~2 days/week of 1 person is needed at minimum. About ~2-3 months of feedback is probably needed for sufficient confidence in a release.