Difference between revisions of "Community Roadmap"

From Horde3D Wiki
Jump to: navigation, search
(Release milestones)
 
(9 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
Our policy is to release often, with atomic changes between two following releases.
 
Our policy is to release often, with atomic changes between two following releases.
  
The current release version is: '''Horde3D 1.0.0 Beta 5'''
+
The current release version is: '''Horde3D 2.0.0'''
  
 
For the future, we planned the following releases:
 
For the future, we planned the following releases:
  
=== Horde3D 1.0.0 (final) ===
+
=== Horde3D 2.1.0 ===
  
* Merge fixes from old [http://hcm-lab.de/public/Horde3D/ SVN Community branch].
+
* Emscripten support
* Improved animation API.
+
* Directional light support
 +
* FBX and gltf 2.0 support in collada (asset) converter
 +
* Extension for debug geometry shapes drawing
 +
* Initial PBR support
 +
* PBR sample
  
=== Horde3D 1.1.0 ===
+
=== Horde3D 2.2.0 ===
  
* Move Overlays to an extension.
+
* New sample that show how to work with different light types, cameras, pipelines and render to texture
* Support for geometry shapes drawing.
+
* OpenGL 4 AZDO (Achieving zero driver overhead) improvements
 +
* Unification of OpenGL backends common functionality
 +
* Multithreaded culling and scene graph updates (partial)
 +
* Basic instancing support
 +
* Reflection probes
  
=== Horde3D 1.2.0 ===
+
=== Horde3D 2.3.0 ===
  
* OpenGL ES2 backend.
+
* Multithreaded rendering
* Support for Android & iOS platforms.
+
* Binary shader (preparation for Vulkan shaders)
 +
* Multithreaded culling and scene graph updates
 +
* Instancing support
  
=== Horde3D 1.3.0 ===
+
=== Horde3D 3.0.0 ===
 
 
* OpenGL 4 backend.
 
* Added support for double precision variables.
 
 
 
=== Horde3D 1.4.0 ===
 
 
 
* Direct3D 11 backend.
 
 
 
=== Horde3D 2.0.0 ===
 
  
 
* Moving scene graph to utility library.
 
* Moving scene graph to utility library.
 +
* Clustered forward (deferred) lighting support.
 
* Model resources.
 
* Model resources.
 
+
* Vulkan support
 +
* Custom memory allocation
 +
* Support for double precision variables.
 +
* Full PBR support, rewrite shader system
  
 
You can follow the progress on this '''GitHub''' page:
 
You can follow the progress on this '''GitHub''' page:
  
https://github.com/horde3d/Horde3D/issues/milestones
+
https://github.com/horde3d/Horde3D/issues
  
 
= Versioning system =
 
= Versioning system =

Latest revision as of 19:27, 15 February 2021

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.

Release milestones

Our policy is to release often, with atomic changes between two following releases.

The current release version is: Horde3D 2.0.0

For the future, we planned the following releases:

Horde3D 2.1.0

  • Emscripten support
  • Directional light support
  • FBX and gltf 2.0 support in collada (asset) converter
  • Extension for debug geometry shapes drawing
  • Initial PBR support
  • PBR sample

Horde3D 2.2.0

  • New sample that show how to work with different light types, cameras, pipelines and render to texture
  • OpenGL 4 AZDO (Achieving zero driver overhead) improvements
  • Unification of OpenGL backends common functionality
  • Multithreaded culling and scene graph updates (partial)
  • Basic instancing support
  • Reflection probes

Horde3D 2.3.0

  • Multithreaded rendering
  • Binary shader (preparation for Vulkan shaders)
  • Multithreaded culling and scene graph updates
  • Instancing support

Horde3D 3.0.0

  • Moving scene graph to utility library.
  • Clustered forward (deferred) lighting support.
  • Model resources.
  • Vulkan support
  • Custom memory allocation
  • Support for double precision variables.
  • Full PBR support, rewrite shader system

You can follow the progress on this GitHub page:

https://github.com/horde3d/Horde3D/issues

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.