BeRTOS Release Policies

BeRTOS is released when there are some new important features and/or bugfixes.

Check release process on  mailing list.

This is the version numbering scheme adopted:

Major.Minor.Revision

• Changes to the revision number must be only both forward and backward compatible. Only bugfixes and very small enhancements are allowed. No new features should be added when revision changes.
• Changes to the minor number must be backward but not forward compatible. New features may be added, but not too many.
• Changes to major number means that the release can be both forward and backward incompatible. A major release should have new features.

Any BeRTOS user can upgrade to backward-compatible releases without any change in the application code. A forward-compatible release means that old application code may take advantages of new features as well, without changes.

Release stabilize policy

Every version of BeRTOS provide a tag on svn repository.

• when we found the first bug in a released version we create a branch in repository named with major.minor of the version
• we use the branch to fix the bug
• when the bug is fixed, we bump up the revision number of this version, and we tag it.
• when the tag is created, we release a new version
• the bugfix is merged on the trunk