Pub. & Maintenance

Publication & Maintenance

Publication and Maintenance are the last two phases in the lifecycle of the Technical Specifications. Documents published by the Organization will contain a URL to raise questions or report bugs.

Publication Task

At this phase, the Project Manager will publish the Technical Documents.

Publish PDF and Releases

After the Ratification of the Technical Specifications, the next phase is the Publication.

• At this step, the Project Manager will publish the Technical Specification via GitHub Pages.

Maintenance Tasks

The Working Group SHOULD maintain the Technical Specifications after publication.

• In this phase, the Working Group MAY receive Issues raised by the Working Group Members or by members of the public.
• The Working Group Approves the Technical documents under a specific Release Version (VX.Y.Z).
• The version of the documents is essential if the Working Group considers applying bug fixes or new features after the publication.

Submit Issues via GitHub

• The Working Group Members MAY raise Issues against the public Technical Specifications.

Triage Issues

As a result of the Issues and Comments submitted against the Specifications, the Working Group MAY decide to update the Specifications.

• It is important to classify the type of changes submitted against already Approved Technical Specifications
• These changes are classified as follows:
  • Editorial or bug fixes, e.g., v1.0 is superseded by v1.0.1
  • Changes that keep the Technical Specifications backward compatible with a previous version, e.g., v1.1 is compatible with v1.0.1
  • Changes that break backwards compatibility, e.g., version v2.0 is not compatible with version v1.4.23 as the major digit X has been changed.