VersioningPolicy - cwtickle/danoniplus-docs GitHub Wiki

English | Japanese

Versioning Policy

In principle, versions are assigned in the format x.y.z (e.g., 18.9.3) in accordance with Semantic Versioning 2.0.0.
For supported versions, see Security Policy for supported versions.

Raise the number x if you have made backward-incompatible changes or major code changes.
Also, if there has been a gap of 100 commits or more since the last major version, and the source code deviates too much, raise the number x,
If there has been a gap of 100 commits or more since the last major version, and we judge that there is a large divergence in the source code, we may raise the number x, regardless of the compatibility status. However, this is limited to cases where there are additions or changes in functionality.
If you have custom sources, please refer to the Migration Guide and consider whether to upgrade.

When minor additions or changes occur, raise the number y **only for the **latest major version. For past versions, the version with the highest number is the one to be modified, except for versions that are no longer supported. In principle, we do not add or change features in past versions, but only make the minimum necessary changes such as bug fixes.
Backward compatibility is maintained as much as possible, but this may not be the case for custom versions. The main changes are in the Update Info and Security Policy.

Raise the number z when a (backward-compatible) bug fix is made to a feature addition or change made in x or y.
If the bug fix is also applied to the supported version, the number z of the supported version will also be raised.
In the case of a feature or code modification that is not a feature addition, but is necessary for source control purposes, If the bug fix is not a feature addition, but is necessary for source control purposes, the z number may be raised instead of the y number.

When the implemented features are large, you may add -M1 or -RC after the version name.
These versions are before the official release, and backward compatibility is not considered.
-M1, -M2, ... is the version under development, and -RC is the release candidate version.
Please note that even release candidate versions may have incompatible fixes afterwards.

If a bug is found before the release and it is after the version number was assigned, the release will be withdrawn, the fix will be implemented, and then the version number z will be raised to accommodate the bug.
- e.g.) If 14.3.0 is withdrawn, the next update will be released as 14.3.1.
If the update after withdrawing a release involves minor additions or changes, the version number y will be raised.