BBAS.Convert - Version History

We attemp to maintain the following convention with regard to assigning version numbers to releases.

1. All version numbers will be specified as three numbers separated by periods (e.g. 4.3.0)
   • The first number will be called the major version number.
   • The second number will be called the minor version number.
   • The third number will be called the bugfix version number.
2. The bugfix version number will be incremented for a release that is not intended to change or add any features, but instead includes fixes for any number of bugs found in the previous version. For example, a release with the same features/functionality as version 4.3.0, but with some bugs fixed that existed in version 4.3.0 would be released as version 4.3.1. The second bugfix release to 4.3.0 would be released as version 4.3.2, and so on.
3. The minor version number will be incremented for any release which adds new functionality (e.g. a new event type, an improved algorithm for an existing event type, a new feature that (hopefully) makes working with the software easier.) These minor releases may also include bug fixes.
4. The major version number will be incremented when there has been some "major" functionality change. The definition of a "major" functionality change is somewhat nebulous, but the following examples of what would be considered a major functionality change should give one the general idea.
   • If support is added for a new digitized datafile type (e.g. AcqKnowledge file format), this would be considered a "major" functionality change.
   • If there is a change of supported platform(s), this would be considered a "major" functionality change. For example, if the program is made available for the Linux Operating System, this will be considered a "major" functionality change.
   These major releases may also include other changes that by themselves would have only constituted a minor release or a bugfix release.

Mail comments or questions to: tbb(at)BioBehaviorAnalysis.com