Development process » History » Version 53
Greg Burri, 12/08/2010 02:42 PM
| 1 | 3 | Greg Burri | h1. Development process |
|---|---|---|---|
| 2 | 1 | Greg Burri | |
| 3 | 16 | Greg Burri | Here is a little list of the development stages involve in Aybabtu. The stages prefixed by '>' are the current stages. |
| 4 | 2 | Greg Burri | |
| 5 | 18 | Greg Burri | # [ok] [[Brainstorming]]. |
| 6 | 33 | Greg Burri | # [ok] [[Functional definition]]. |
| 7 | # [ok] Defining of technologies, [[libraries]] and [[tools]]. |
||
| 8 | # [ok] Creating of some [[prototypes]] to validate the point above. They will be reused during the implementation stage. |
||
| 9 | 42 | Greg Burri | # [ok] Technical specifications. [[Protocols]], [[algorithms]] and [[persistent data]]. Some prototypes can be added to test algorithms or anything else. |
| 10 | 47 | Greg Burri | # [ok] [[Architecture]] of components and theirs interface. -> Component Diagrams. |
| 11 | # [ok] Modeling of each components. -> Class diagram, sequence diagram, state diagram, etc.. |
||
| 12 | 53 | Greg Burri | # > 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. |
| 13 | 43 | Greg Burri | # Alpha version. |
| 14 | 46 | Greg Burri | ** The _1.0_ branch is created |
| 15 | 50 | Greg Burri | ** All features are implemented. |
| 16 | 51 | Greg Burri | # Beta versions. |
| 17 | 1 | Greg Burri | ** The tag _1.0 beta1_ is created. |
| 18 | 52 | Greg Burri | ** Testing with people who didn't participate in the project. |
| 19 | 53 | Greg Burri | ** Profiling, optimizing, simplification and stabilisation. See [[Stabilisation process]] |
| 20 | 51 | Greg Burri | ** After some corrected bugs an another beta is created if necessary (beta1, beta2, etc..). |
| 21 | 38 | Greg Burri | # Final Release \o/ (before Starcraft 2 release if possible ^-^´) |
| 22 | 46 | Greg Burri | ** The tag _1.0_ is created |
| 23 | 45 | Greg Burri | # Define the future integration workflow[1] with _git_ and Goto 1.. |
| 24 | |||
| 25 | fn1. http://www.whygitisbetterthanx.com/#any-workflow |