Package Naming and Versioning

Package name format: For example: oglib_string-2.3-2
 * PkgName-MajorVersion.MinorVersion[.FixVersion[.BuildNumber]]-PkgVersion


 * PkgName - the name of the package (e.g., oglib_string)
 * MajorVersion - the major version number. Incrementing this number indicates that some major changes have occurred and the package might not be compatible with older versions. OpenG packages based on LabVIEW 8.2 will have major version 3
 * MinorVersion - the minor version number. This indicates that some new features have been added the package, but that it is still compatible with older versions containing the same major version number.
 * FixVersion (optional) - the patch/bugfix version number. This is used to indicate that the only changes to a package are minor fixes.
 * BuildNumber (optional) - the build number. This number is incremented each time a package is built.  It is useful to distinguish between unreleased development builds.
 * PkgVersion - the package version number. This is used to indicate that the package has changed but the thing being packaged has not changed.  For example, if the package's description changes, but there are no changes to the library itself.

For a package to be compatible with a previous (minor version) release it must not:


 * BREAK CODE!
 * CAUSE APPS TO RUN DIFFERENTLY!
 * Remove any public VIs
 * Remove any terminals or change the connector pane pattern of any public VI
 * Add new required terminals of any public VI (or change existing terminals to required) - (non-required terminals, may be added, but not wiring them should cause a default behavior identical to the previous release)
 * Rename any of any public VIs
 * Change the behavior of any public VIs