Difference between revisions of "Community Roadmap"
| Line 5: | Line 5: | ||
= Release milestones = | = Release milestones = | ||
| + | |||
| + | 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 1.0.0 Beta 5''' | ||
| + | |||
| + | For the future, we planned the following releases: | ||
=== Horde3D 1.0.0 (final) === | === Horde3D 1.0.0 (final) === | ||
| − | * | + | * Merge fixes from old SVN Community branch. |
* Improved animation API. | * Improved animation API. | ||
=== Horde3D 1.1.0 === | === Horde3D 1.1.0 === | ||
| + | |||
| + | * OpenGL ES2 backend. | ||
| + | * Support for Android & iOS platforms. | ||
| + | |||
| + | === Horde3D 1.2.0 === | ||
* Direct3D 11 backend. | * Direct3D 11 backend. | ||
| − | === Horde3D 1. | + | === Horde3D 1.3.0 === |
* OpenGL 4 backend. | * OpenGL 4 backend. | ||
Revision as of 13:50, 4 October 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.
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 Beta 5
For the future, we planned the following releases:
Horde3D 1.0.0 (final)
- Merge fixes from old SVN Community branch.
- Improved animation API.
Horde3D 1.1.0
- OpenGL ES2 backend.
- Support for Android & iOS platforms.
Horde3D 1.2.0
- Direct3D 11 backend.
Horde3D 1.3.0
- OpenGL 4 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.)
