Guide to releasing software at Q-CTRL
Every software release at Q-CTRL requires three important pieces of information:
The information is mandatory and follows specific standards that MUST be followed in order to ensure consistency, quality and usefulness for both internal and external customers.
The version MUST follow the Semantic Versioning standard.
The title MUST be the project name followed by the version. For example,
Q-CTRL Python Open Controls 2.3.4.
The description MUST consist of at least one of the following sections:
- Breaking changes
- What’s new
- Bug fixes
|Breaking changes||A list of backwards-incompatible changes to the public API|
|What’s new||A list of new features or functionality a customer would experience or have access to|
|Bug fixes||A list of bugs fixed as part of the release|
The sections MUST appear in the above order. If one section is empty, it can be omitted from the description. The contents of each section MUST be an unordered (bulleted) list and MUST adhere to the Q-CTRL style guide.
Use the template below when describing a release.
Breaking changes - Things - We - Broke What's new - Things - We - Added Bug fixes - Things - We - Fixed
Sometimes a release is necessary because of an updated dependency. For example, the Q-CTRL Python package being released because of an updated version of the Q-CTRL Commons Python package. Although the changes may only occur in the dependency project, the changes affecting the upstream project MUST be captured in the release description of that project.