SKAMPI v0.13.0

Proposed Release Feature Overview

• Taranta re-enabled
• Minor CI Pipeline improvement updates
• Documentation clean-up

Background

This is a proposed release of SKAMPI at the end of / during PI13.

The idea behind this release is to try out a SKAMPI version numbering scheme, which is

• in line with Release-on-demand principles;
• SemVer compliant:
  • MAJOR as stability & backward compatibility indicator
  • MINOR as next/current-PI indicator
  • PATCH as needed/useful - see below
• Indicates a PI number in order to place the version in a temporal sense, that makes it easy enough for stakeholders across the project to reason about. Examples:
  • A <MAJOR>.X.Y release can be made at the end of PI X, for demonstration purposes. This means that all patch releases can be linked to genuine patches or Sprints (if no other patching is required)
  • more examples needed?
• Allows for the PATCH numbers to be used for Sprint numbers without a hard requirement - if 10 releases end up being made during a PI this number potentially becomes a metric in itself which could be reasoned about, but this is not important.