Difference between revisions of "Community Roadmap"

From Horde3D Wiki
Jump to: navigation, search
(Versioning system)
Line 30: Line 30:
  
 
<blockquote>
 
<blockquote>
<b>MAJOR</b> version when you make incompatible API changes,
+
<b>MAJOR</b> version when we make incompatible API changes,
 
<br/>
 
<br/>
<b>MINOR</b> version when you add functionality in a backwards-compatible manner, and
+
<b>MINOR</b> version when we add functionality in a backwards-compatible manner, and
 
<br/>
 
<br/>
<b>PATCH</b> version when you make backwards-compatible bug fixes.
+
<b>PATCH</b> version when we make backwards-compatible bug fixes.
 
</blockquote>
 
</blockquote>
  
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
+
Additional labels for pre-release and build metadata are used when necessary ('''i.e.:''' ''Alpha'', ''Beta'', ''Release Candidate'', etc.)

Revision as of 16:18, 30 September 2013

A deprecated version of this Roadmap is available at: Community Roadmap deprecated.


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

The current release version is: Horde3D 1.0.0 Beta 5

Horde3D 1.0.0 (final)

  • OpenGL ES2 backend.
  • Improved animation API.

Horde3D 1.1.0

  • Direct3D 11 backend.
  • Added support for double precision variables.

Horde3D 2.0.0

  • Moving scene graph to utility library.
  • Model resources.

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.)