The First Release
Posted: Fri Feb 02, 2007 4:44 pm
I know we all have exams, but before everyone starts learning I would like to collect some ideas about the first release. I think Orxonox is at a point where we shuold make a first release. Not a version to play hundreds of hours, but a release that shows what Orxonox can do, to attract new developers and to make it more popular. My questions (and my answers).
1. When should we release?
2. What kind of development model should we use in the future?
3. Version number? Release name?
4. What should the release contain? What has to be solved?
-------------------------
Answers:
-------------------------
1. When should we release?
I think we should release it before the new PPS starts. After the exams, there will be no snow left... so we have time
-------------------------
2. and 3.
We should make incremental releases like many OSS Projects do. These releases will only receive bug fixes, no new features.
So out first release would be 0.1.0, All bug-fixes are 0.1.x . The second release 0.2.0. And so on. If we are stable and have 100h+ content we'll release 1.0.0
Better Ideas? And we need funny release names...
-------------------------
4. What should the release contain? What has to be solved?
We shouldn't add any new features. Just improve the existing code and add a level that shows the modules of the previous PPSs.
- improve the scroller level (segfault(s)).
- fix the missing weapons (rockets).
- fix the rotor.
- check if shaders are supported (segfault).
- Add a Tech-Demo-Level (camera only, scripted) with a vulcano, a lake, the weather engine and a movie screen with the Orxonox cartoon.
- Add a "credits" level.
- Add the "multiplayer arena" as a proof of concept multiplayer level (low priority, maybe very unrealistic)
Other things (post release):
- Windows installer
- ebuild and packages for as many distributions as possible Ubuntu is already maintained.
- Linux Installer
-------------------------
Your opinions? What did I forget?
1. When should we release?
2. What kind of development model should we use in the future?
3. Version number? Release name?
4. What should the release contain? What has to be solved?
-------------------------
Answers:
-------------------------
1. When should we release?
I think we should release it before the new PPS starts. After the exams, there will be no snow left... so we have time
-------------------------
2. and 3.
We should make incremental releases like many OSS Projects do. These releases will only receive bug fixes, no new features.
So out first release would be 0.1.0, All bug-fixes are 0.1.x . The second release 0.2.0. And so on. If we are stable and have 100h+ content we'll release 1.0.0
Better Ideas? And we need funny release names...
-------------------------
4. What should the release contain? What has to be solved?
We shouldn't add any new features. Just improve the existing code and add a level that shows the modules of the previous PPSs.
- improve the scroller level (segfault(s)).
- fix the missing weapons (rockets).
- fix the rotor.
- check if shaders are supported (segfault).
- Add a Tech-Demo-Level (camera only, scripted) with a vulcano, a lake, the weather engine and a movie screen with the Orxonox cartoon.
- Add a "credits" level.
- Add the "multiplayer arena" as a proof of concept multiplayer level (low priority, maybe very unrealistic)
Other things (post release):
- Windows installer
- ebuild and packages for as many distributions as possible Ubuntu is already maintained.
- Linux Installer
-------------------------
Your opinions? What did I forget?