Description of release management of documents related to transmission of payment messages.

1. Revision history

1.1. Version 1.x

1.1.1. Version 1.0.0

Issue Description Severity

None

Initial version

Major

1.2. Contributors

  • Erlend Klakegg Bergheim, Agency of Public Management and eGovernment

  • Olav Astad Kristiansen, Agency of Public Management and eGovernment

2. Scope

This document descibes the process for release management of documents related to transmission of payment messages.

Documents part of this release management:

  • Packaging of ISO 20022 financial documents

  • Payment Extras

  • Payment processes

  • Release management

  • Requirements for Access Points

  • Rulebook

  • Security requirements for secure file transactions

  • Use of (enhanced) PEPPOL eDelivery network for exchange of ISO 20022-based payment messages

Release management of documents, specifications, etc. provided by OpenPEPPOL referenced from above documents is handled by OpenPEPPOL and is out of scope for this document.

Release management of documents, specifications, etc. provided by Agency of Public Management and eGovernment (Difi) referenced from above documents is handled by Difi and is out of scope for this document.

3. Responsibilites

Bits:

  • Acting as pricipal owner of all documents.

  • Coordinating dialog on behalf of the banks with regard to new releases.

Agency of Public Management and eGovernment:

  • Publishing and maintaining all documents.

  • Coordination of releases.

4. Versioning

Documents related to transmission of payment messages are versioned heavily inspired by Semantic Versioning. Additional labels are not used.

4.1. Patch versions

Description of changes part of patch releases:

  • Textual clarifications
    Improvment of documents to ensure equal understanding of content.

  • Updating code lists
    Adding new codes and removing codes already phased out.

Updates do patch versions are mandatory as of publication date unless otherwise stated.

4.2. Minor versions

In addition to changes part of patch versions, this changes may be part of minor releases:

  • Adding and removing support for new algorithms
    Adding new algorithms to be suppored and removing algorithms aldready phased out.

  • New requirements
    Adding support for new requirements and new features.

Each change triggering minor version will have a defined period of phase-in and phase-out.

4.3. Major versions

New major versions are exptected to contain breaking changes. Publication of major versions contains a pre-defined date when then version is mandatory in addition to period for phase-in of the new version and phase-out of previous major version.

5. Schedule

Major (X.0.0) Minor (y.X.0) Patch (y.y.X)

Potential notification

September 1st
(year 1)

March 15th
September 15th

December 15th
March 15th
July 15th
September 15th

Potential review

March 1st
(year 2)

April 15th
October 15th

January 15th
April 15th
August 15th
October 15th

End of review

August 1st
(year 2)

May 5th
November 5th

February 5th
May 5th
September 5th
November 5th

Potential release

September 1st
(year 2)

May 15th
November 15th

February 15th
May 15th
September 15th
November 15th

Notifications must be available at the defined date or earlier. Notification may contain minor changes (extending amount of days) to the release schedule for the given release to avoid Fridays, weekends and public holidays.

5.1. Implementation

Active use of periods of phase-in and phase-out are used to handle changes without having to create a major versions.

Implemententation of changes is done by the individual implementer. Implementations must be updated according to updated documents within the communicated timeframe.

6. Publication

  • All notifications are published on VEFA as announcements (RSS supported).

  • All updated documents are made available on VEFA side by side current versions during review. Previous versions are removed from the portal when new versions are released.

  • Aggredated release note is provided as part of each release.