List view
Implementation/packaging issues that need to be dealt with before we can feel comfortable releasing a Primer 1.0 package set. After this point, we will need to be careful about making API changes, following PvP/semver, etc.
No due date•1/23 issues closedAdd an effects system, plus any other definitional changes required as a result of field use.
No due date•0/2 issues closedPerformance improvements and UX-related improvements based on field use.
No due date•0/4 issues closedThe final specification for Primer 1.0 (pure language, no effects). This should be Primer 0.9, which will be a feature-complete pure language, plus any changes required as a result of student & teacher testing.
No due date•0/4 issues closedA pure version of Primer (no effects) that is more or less feature complete, but may still incorporate (possibly major) changes based on student testing.
No due date•0/2 issues closedRelease a pure implementation of Primer (no effects). This release will probably be missing a few tricky typedef editing scenarios, but will otherwise be mostly feature-complete.
Overdue by 1 year(s)•Due by December 14, 2023•13/18 issues closedSupport for a proper open source release.
No due date•17/24 issues closed