Version and Deprecation Policies

In Janus projects, version numbers semantic is given by Table 1 and associated constraints are explained on this page.

Table 1: Details of the Components of a Version Number

Part Details
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.

Run Policies

  • Major number 0 means incubating version. The following constraints on major numbers are discarded.
  • Let x and y two major numbers, so that x \neq y; 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.

Deprecation Policies

  • 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.


Related Pages

2016-01-24SARL 0.3.1 and Janus 2.0.3.1 are available.
2015-11-30SARL 0.3.0 and Janus 2.0.3.0 are available.
This page was last modified on 17 February 2011, at 10:42. This page has been accessed 3,508 times.
Copyright 2010-2017 © Janus Core Developers - Privacy policy