Versioning (EN)

vglobal_feature_fits_with_roadmap.total_count_of_commits_of_current_branch (как пример: v1.2114)

The first value of version (before '.') fits with following:

• Reduce total size of repository and restructured project which can't follow of OpenXRay's structure (v0.xxxx)
• Rewritten all lua scripts to C++ (v1.xxxx)
• Written own SDK (v2.xxxx)
• Created own renderer based on Vulkan API (~ v3.xxxx)
• In-Game Physics based on Bullet Physics (~ v4.xxxx)
• Vector UI based on HTML/CSS usage (~ v5.xxxx)
• Fixed animation, character animations (~ v6.xxxx)
• Supported C++26 and removed all previous legacy of standards, used all features (as it can) of C++20 (~ v7.xxxx)
• Remove all unused libraries (~ v8.xxxx)
• Cleanup code base, write all code in one code style (~ v9.xxxx)
• Pathfinding based on navigation mesh usage (~ v10.xxxx)
• For serializable data we will use JSON (but it can be some excludes) (~ v11.xxxx)
• Trying to reduce total inheritance of client classes (optimization) (~ v12.xxxx)
• Delete server part of project (~ v13.xxxx)
• Rewrite all libraries to modules (but that feature can implemented only at C++26) (~ v14.xxxx)
• PBR (~ v15.xxxx)
• Clouds (graphics) (~ v16.xxxx)
• Sound Occlusion (~ v17.xxxx)

The section 3 to last can't be clearly set up. I mean the number of current version (first number) can't guaranteed that appropriate description will exist for it. v3.xxxx can describe implementation of physics, but (not as matched in this wiki-page) Vulkan API. Just checks the description of tag's version.

Contributors (EN)