This milestone includes critical issues identified after the open-release/teak.master branch cut, as well as important unresolved issues from previous testing cycles. These issues are prioritized for inclusion in the Teak.1 release and typically meet one or more of the following criteria (non-exhaustive):

• Already have a fix available and are easy to include
• Considered release blockers
• Involve security vulnerabilities
• Affect the stability of new features
• Uncover regressions caused by major changes
• Are significant or high-priority issues impacting core functionality
• Carryover issues from prior releases that didn’t make the cut but remain relevant

The BTR team actively works to get these issues resolved before the Teak.1 release is finalized.