General release requirements

Scope: managed applications, mobile applications, and ordinary applications.

1. When a new release is published, the version or revision number must be incremented.

2. The changes in a revision are usually limited by bug fixes and some minor changes. A new revision must support seamless data migration from the previous revision.

3. Version is reserved for major changes that have widespread effects on the configuration and require data modification. A general marker of a version—however, non-obligatory—is that the application must convert its data to update to a newer version. When developing a new version, try to implement automatic data migration algorithms. Otherwise, write a migration guide that describes the necessary steps in detail.

See also:

Version numbering

<< Prev Next >>