List view
Stabilize the CI/CD and release setup after the branch rename, simplify the release flow, and harden package publishing and version management.
Due by May 15, 2026•7/8 issues closedFocus on the final improvements needed to make the package more stable, polished, and ready for wider adoption.
No due dateRefresh docs and examples to make the package easier to learn and use.
No due dateImprove coverage and strengthen CI checks for core workflows.
No due dateAdd reliable persistence and reproducible training workflows.
No due dateSimplify the API and make configuration more consistent across models.
No due date•0/3 issues closedDefine the stable core, experimental scope, and supported package baseline.
No due date•0/3 issues closedTriton Implementation
Overdue by 1 year(s)•Due by April 1, 2025•3/5 issues closed