Release Cycle

The most fundamental aspect to understanding the release cycle is understanding how FMSLogo version numbers work. FMSLogo uses three numbers for its version number, separated by dots, as in:

FMSLogo major.minor.bugfix

For example, FMSLogo 6.10.1 has a major version of 6, a minor version of 10, and a bugfix version of 1. In addition, there are "developer snapshots" versions that are not publicly released. Developer snapshots may be completely untested. Developer snapshots are distinguished from "official" revisions by appending a "+" character to the most recent revision.

A change to the bugfix version is required by any of the following:

A change to the major version is required by any of the following:

Before I release any new version of FMSLogo, I run it through a regression test suite on Windows XP. This includes automated tests, manual tests, and testing that the "extras" still work correctly.

I don't follow a release schedule for major or minor versions of FMSLogo. Development is done on an ad-hoc basis when I have time and inclination. I generally release a new version when I judge that it has been too long since the previous one and there are enough changes that justify a new version. I also release a new version when someone states a specific need for a bugfix or feature. So if there is an unreleased change that you want, be sure to speak up.

I release a new bugfix version only when necessary. Due to the amount of time required to test each version of FMSLogo, I only release a bugfix version to address problems that can't wait until the next minor revision. In other words, if I release a bugfix version, it's because I did something very bad in the previous release.