OGRE Wiki
Support and community documentation for Ogre3D
Ogre Forums
ogre3d.org
Log in
Username:
Password:
CapsLock is on.
Remember me (for 1 year)
Log in
Home
Tutorials
Tutorials Home
Basic Tutorials
Intermediate Tutorials
Mad Marx Tutorials
In Depth Tutorials
Older Tutorials
External Tutorials
Cookbook
Cookbook Home
CodeBank
Snippets
Experiences
Ogre Articles
Libraries
Libraries Home
Alternative Languages
Assembling A Toolset
Development Tools
OGRE Libraries
List of Libraries
Tools
Tools Home
DCC Tools
DCC Tutorials
DCC Articles
DCC Resources
Assembling a production pipeline
Development
Development Home
Roadmap
Building Ogre
Installing the Ogre SDK
Setting Up An Application
Ogre Wiki Tutorial Framework
Frequently Asked Questions
Google Summer Of Code
Help Requested
Ogre Core Articles
Community
Community Home
Projects Using Ogre
Recommended Reading
Contractors
Wiki
Immediate Wiki Tasklist
Wiki Ideas
Wiki Guidelines
Article Writing Guidelines
Wiki Styles
Wiki Page Tracker
Ogre Wiki Help
Ogre Wiki Help Overview
Help - Basic Syntax
Help - Images
Help - Pages and Structures
Help - Wiki Plugins
Toolbox
Freetags
Categories
List Pages
Structures
Trackers
Statistics
Rankings
List Galleries
Ogre Lexicon
Comments
History: Development Procedures
View page
Source of version: 11
(current)
{maketoc} !General development procedures ((Integrating API documentation into Qt Creator Help)) !Ogre development procedures This is how Sinbad describes in 2010 the development process of Ogre3D (quoted from ogre3d forums): {QUOTE(replyto="Sinbad")}In practice, what happens even now is this: * Developer X has a need / desire to add a major feature or make a key change. * X proposes it to the community, gets feedback & iterates * X leads the implementation, doing the majority of the main work but with help for platform portability, bugs they missed, etc * Over time X is considered the 'owner' of this feature and gets consulted on changes to it out of courtesy and for reference, but broadly the whole team and community hack on it incrementally * At all times, everyone is working within our established design and coding patterns to ensure consistency, platform compatibility, etc{QUOTE} Here you'll find some general information about being an OGRE developer. * [http://ogre.svn.sourceforge.net/viewvc/ogre/trunk/Docs/CodingStandards.html|Coding Standards] * ((Merging Branches)) * ((Subversion settings)) * ((Building the manual)) * ((Preparing a new Release)) --- Alias: (alias(DevelopmentProcedures))
Search by Tags
Search Wiki by Freetags
Latest Changes
IDE Eclipse
FMOD SoundManager
HDRlib
Building Ogre V2 with CMake
Ogre 2.1 FAQ
Minimal Ogre Collision
Artifex Terra
OpenMB
Advanced Mogre Framework
MogreSocks
...more
Search
Find
Advanced
Search Help
Online Users
141 online users