Release Rules

Release Rules

When each new version of InaSAFE is released it must adhere to the following stringent quality measures:

Testing:

At least 2/3rds of all lines of code must be successfully exercised by a regression test suite which is distributed alongside the software itself.

Clarity:

The software complies with the appropriate development standards for the language used, i.e. the coding style guide and has been peer reviewed.

Disclaimer:

The software includes a clear Disclaimer of Warranty and appropriate Limitation of Liability clause. In this case this is achieved by using the GNU General Public Use v3 License.

HIstory:

The software is maintained in a source control system which allows full visibility of its history, tracking of issue resolution and potential reversal of past changes.

Authenticity:

Source control system codes uniquely identify each individual version of the software making it possible to verify its origin.

After these stringent quality measures have been met there must be signature from the majority of the allocated committee.

For a Major release it requires approval and signature from a majority of the PSC

For a Minor release it requires approval from a majority of the TWG.

For a Point release it requires only approval from any of the TWG members.

Definition of software release levels for the InaSAFE project

InaSAFE is built as an add-on to QGIS so has adopted the conventions used in QGIS:

Major releases are versions that provide significant improvements to the software. A major release may change both the user interface and the underlying programming interface. Major releases are numbered as 1.0.0, 2.0.0, …

Minor releases provide extensions and improvements to the software. They possibly modify the user interface but must maintain compatibility with the existing programming interface. Minor releases are numbered as 1.1.0, 1.2.0, …

Point releases contain corrections of errors, optimizations and small improvements that maintain compatibility with both the user interface and the programming interface. Point releases are numbered as 1.1.1, 1.1.2, …

Disclaimer:InaSAFE has been jointly developed by the Indonesian Government-BNPB, the Australian Government, the World Bank-GFDRR and independent contributors. These agencies and the individual software developers of InaSAFE take no responsibility for the correctness of outputs from InaSAFE or decisions derived as a consequence.