The District of Joban JCM:Versioning Scheme

JCM:Versioning Scheme

From The District of Joban
Revision as of 00:05, 2 November 2023 by LX86 (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Note

This article is created for Joban Client Mod v2.0.0.
Features mentioned might not be available to the public yet.

To help eliminate confusion, a consistent versioning scheme is proposed to be applied in JCM 2.0.0.

Major Update

Major update are updates with significant structural changes in code. In an ideal situation where the code developed works well, this number would never need to be bumped.

This is defined by the first number in the version number: 2.0.0 (The 2nd major update)

Feature Update

Feature update are regular update that may contain new features/add new contents.

This is defined by the second number in the version number: 2.4.0 (The 4th feature update)

Bug Fixes / Minor patch

Bug Fixes / Minor patch are very minor updates that fixes critical bugs or have their language files updated, a minor update should never change any behavior for the user nor have any new contents or features added.

This is defined by the third number in the version number: 2.0.3 (The 3rd minor update patch)

Pre-release

Pre-release updates are only issued before a major update (Not feature update!) is officially released due to the relatively smaller scale of JCM.

This is defined by the following suffix in the version number: 2.0.0-prerelease.3 (The 3rd pre-release version)

Minecraft Version Suffix

In the downloadable jar file of Joban Client Mod, the filename and the in-game version number would also need to indicate the Minecraft Version it is intended to use for.

This is defined by the following suffix in the version number: 2.0.0+1.20.2 (Designed for use in Minecraft 1.20.2)