Version and Deprecation Policies
In Janus projects, version numbers semantic is given by Table 1 and associated constraints are explained on this page.
|Major||This value represents the version number for the application. The number will be increased each time there is a major change in functionality or a huge revision of the underlying architecture.|
|Minor||This value is reset to 0 for every increase of the Major value. It will be increased when new functionality has been added, or when significant fixes have been made after problems have been reported.|
|Revision||This value is reset to 0 for every increase of the Minor value. It will be increased when fixes have been applied after problems have been reported.|
- Major number 0 means incubating version. The following constraints on major numbers are discarded.
- Let x and y two major numbers, so that ; source code running on x has no warranty to be runnable on y.
- Let m a major number, and x, and y two minor numbers so that x < y; all source codes running on m.x must be also runnable on version m.y.
- When increasing major number, all the deprecated feature coming from the previous major version are removed.
- Let m a major number, and x, and y two minor numbers so that x < y; in a feature is available on m.x and should disappear on m.y, it must be tagged as deprecated.