Release Goals Route

SquirrelJME follows a goal-oriented release plan rather than one of fixed dates. This is to reduce stress and not put hard time limits but more of an action-oriented plan to meet when it is time for releases.

Until all the goals are met (or otherwise pushed back or dropped if needed) the lowest version number will remain at zero. Otherwise, when the goals are met the Release Candidate process will start.

To reduce the possibility of releases failing due to issues, there will be a release candidate as a kind of test to ensure that the release process works and that SquirrelJME actually functions. There will be as many release candidates as needed for the fixing of issues, however once the release is determined to be stable enough it will then become an actual release and get an even numbered release version.

Effectively in short, these act as the major milestones that must be met before a release is even possible.

Please note that this information may change over time and is just speculation based on project planning.

0.2.0 (December 25, 2018)

This is the first version of SquirrelJME.

This release was before the goal-oriented release planning.

0.4.0 (2026 TBD)

As of 2026/06/28: 206 of 317 (64%)

[| 0%...|10%...|20%...|30%...|40%...|50%...|60%...|70%...|80%...|90%...|]
[|||||||||||||||||||||||||||||||||||||||||||||..........................]

0.6.0 (TBD)

0.8.0, 0.10.0, 0.12.0, 0.14.0, etc. (TBD)

These versions are too far in the future for any realistic planning.

1.0.0 (TBD)

This version is too far in the future for any realistic planning.

1.2.0 (TBD)

This version is too far in the future for any realistic planning.