About Version Numbers
Siteframe uses a fairly standard version numbering scheme:
major . minor . patch
where major is the major version number (e.g., "5"), minor is a minor release (usually with significant enhancements), and patch is incremented with each new formal relase. Typically, a major release involves a substantial rewrite of the code or major new enhancements. A minor release indiciates relatively smaller fixes or enhancements, and a patch release can often be for a single change.
Siteframe distributions usually also have a build number; the build number is incremented consecutively throughout the life of a project, and is only used (in rare cases) to determine if a file is newer or older than another file.
Distribution files are usually named:
beaumont-version-build.tar.gz
where version and build are described above. Usually, there is only one build per version (formal release). On rare occasions, a bug might be discovered immediately upon a new version's release, so another version of the file with the same version number but a new build might be made available within a few minutes.
Within templates, both the version number and build number are available as the Smarty variables {$VERSION} and {$BUILD}. These can be useful; for example, many of the standard template sets use a CSS include tag like this:
<style type="text/css" href="/path/to/your/css?v={$BUILD}" />
The fact that the {$BUILD} version is different with every new release will ensure that browsers no longer cache the old version of the CSS file and instead fetch the new version from the server. This same technique can be applied to images (such as site logo files).
