Difference between revisions of "Community Roadmap"
(→Release milestones) |
(→Horde3D 2.0.0) |
||
Line 34: | Line 34: | ||
* Vulkan support | * Vulkan support | ||
* Custom memory allocation | * Custom memory allocation | ||
+ | * PBR support | ||
You can follow the progress on this '''GitHub''' page: | You can follow the progress on this '''GitHub''' page: |
Revision as of 12:50, 1 October 2017
As a way to keep the community in touch with the development of Horde3D project, this page will keep an up to date log of the official Roadmap for next releases.
Contents
Release milestones
Our policy is to release often, with atomic changes between two following releases.
The current release version is: Horde3D 1.0.0
For the future, we planned the following releases:
Horde3D 1.1.0
- Move Overlays to an extension.
- Support for geometry shapes drawing.
- Directional light support
- Material class performance improvements
- Multithreaded culling and scene graph updates
Horde3D 1.2.0
- OpenGL ES3 backend.
- Support for Android & iOS platforms.
- Instancing support
Horde3D 1.3.0
- OpenGL 4 AZDO (Achieving zero driver overhead) improvements.
- Support for double precision variables.
Horde3D 2.0.0
- Moving scene graph to utility library.
- Model resources.
- Vulkan support
- Custom memory allocation
- PBR support
You can follow the progress on this GitHub page:
https://github.com/horde3d/Horde3D/issues/milestones
Versioning system
The Horde3D project is following SemVer 2.0 definition.
Basically it means that, given a version number MAJOR.MINOR.PATCH, we increment the:
MAJOR version when we make incompatible API changes,
MINOR version when we add functionality in a backwards-compatible manner, and
PATCH version when we make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are used when necessary (i.e.: Alpha, Beta, Release Candidate, etc.)
A deprecated version of this Roadmap is available at: Community Roadmap deprecated. |