Development process » History » Revision 52
Revision 51 (Greg Burri, 11/18/2009 09:08 PM) → Revision 52/58 (Greg Burri, 11/18/2009 09:08 PM)
h1. Development process Here is a little list of the development stages involve in Aybabtu. The stages prefixed by '>' are the current stages. # [ok] [[Brainstorming]]. # [ok] [[Functional definition]]. # [ok] Defining of technologies, [[libraries]] and [[tools]]. # [ok] Creating of some [[prototypes]] to validate the point above. They will be reused during the implementation stage. # [ok] Technical specifications. [[Protocols]], [[algorithms]] and [[persistent data]]. Some prototypes can be added to test algorithms or anything else. # [ok] [[Architecture]] of components and theirs interface. -> Component Diagrams. # [ok] Modeling of each components. -> Class diagram, sequence diagram, state diagram, etc.. # > Implementation of each component with unit tests, unit benchmarks, and code coverage. Once a component is near finished, a another person of the team will read the code and criticize it in a positive way. # Alpha version. ** The _1.0_ branch is created ** All features are implemented. ** Profiling, optimizing, simplification and stabilisation. See [[Stabilisation process]] # Beta versions. ** The tag _1.0 beta1_ beta_ is created. ** Testing with people who didn't participate in the project. ** After some corrected bugs an another beta is created if necessary (beta1, beta2, etc..). # Final Release \o/ (before Starcraft 2 release if possible ^-^´) ** The tag _1.0_ is created # Define the future integration workflow[1] with _git_ and Goto 1.. fn1. http://www.whygitisbetterthanx.com/#any-workflow