List view
This milestone is for general maintenance work that isn’t tied to a specific release or project. It includes: * Configuration improvements * Dependency management * Low-priority or internal cleanup tasks Used to track non-feature work essential for platform stability.
No due date•0/18 issues closedFinal release in the Teak cycle, used for: * Remaining bug fixes and regressions not addressed in Teak.2 * Safe fixes from previous test cycles that are still relevant * Final polishing and cleanup before transitioning to the next Open edX release Like Teak.2, this release is strictly for stabilization and long-term support.
Due by October 9, 2025This milestone includes issues targeted for the Teak.2 release, including: * Bugs or regressions discovered after Teak.1 * Low- to medium-priority issues from earlier testing cycles that couldn’t be included in Teak.1 * Community-reported issues with safe and validated fixes * Backports from the main branch that improve stability No new features are introduced. Teak.2 focuses on post-release corrections and stabilization.
Due by August 9, 2025This 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.
Overdue by 12 day(s)•Due by June 9, 2025•43/53 issues closed